Re: RFC - AppConfig::DBI - support for DBI connection (info) via AppConfig

I realize this smacks of the whole "class name does not imply relationship" argument, but AppConfig::DBI reads to my brain as a DBI persistence/store implementation of AppConfig data, not an AppConfig store of DBI-related information. Would DBI::AppConfig be just as ambiguous? Maybe, I'm not sure. But it would seem more intuitive to me, since you are using AppConfig to a DBI-suited end, to augment DBI.

--rjray

Comment on Re: RFC - AppConfig::DBI - support for DBI connection (info) via AppConfig

Replies are listed 'Best First'.
Re: Re: RFC - AppConfig::DBI - support for DBI connection (info) via AppConfig by princepawn (Parson) on Mar 03, 2002 at 14:52 UTC
Would DBI::AppConfig be just as ambiguous? Maybe, I'm not sure. But it would seem more intuitive to me, since you are using AppConfig to a DBI-suited end, to augment DBI. It would have to be `DBIx` not DBI as DBI is reserved by the DBI distribution Actually the real thing missing from the module name is `Connect` which is what this module is supposed to be for! `DBIx::Connect->to('dev_db'); DBIx::Connect->data_for('dev_db');` [download] HEY! I like it!!!	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Re: RFC - AppConfig::DBI - support for DBI connection (info) via AppConfig
by princepawn (Parson) on Mar 03, 2002 at 14:52 UTC

Would DBI::AppConfig be just as ambiguous? Maybe, I'm not sure. But it would seem more intuitive to me, since you are using AppConfig to a DBI-suited end, to augment DBI.

It would have to be DBIx not DBI as DBI is reserved by the DBI distribution
Actually the real thing missing from the module name is Connect which is what this module is supposed to be for!
```
DBIx::Connect->to('dev_db');
DBIx::Connect->data_for('dev_db');
[download]
```
HEY! I like it!!!

[reply]
[d/l]
[select]