package My::DBI::Config;
use base qw/Class::DBI/;
My::DBI::Config->set_db { ...
[download]

package My::DBI;
use base qw(My::DBI::Config);
[download]

See the docs:

     Give it a database connection
           Class::DBI needs to know how to access the database.  It do
+es this
           through a DBI connection which you set up by calling the se
+t_db()
           method.

                   Music::DBI->set_db('Main', 'dbi:mysql:dbname', 'use
+r', 'password');

           By setting the connection up in your application base class
+ all the
           table classes that inherit from it will share the same conn
+ection.
[download]

I keep my connection info in a config file, so I'll have something like library.site.conf that includes

DB_NAME         = library
DB_HOST         = localhost
DB_USER         = username
DB_PASS         = password
[download]

package MyDatabase::DBI;
use base qw(Class::DBI::mysql);
my %config;
use Config::General;
my $conf = new Config::General(
  -ConfigFile => '/usr/local/configfiles/library.site.conf',
  -InterPolateVars => 1
                              );
%config = $conf->getall;

my $dsn = "DBI:mysql:host=$config{DB_HOST};database=$config{DB_NAME}";
my $db_user = $config{DB_USER};
my $db_pass = $config{DB_PASS};

__PACKAGE__->set_db('Main', $dsn, $db_user, $db_pass);
# etc.
[download]

There are a ton of similar ways to do this.

...to Class::DBI rather than hard-coding it in the source for your subclass?

hmm.. there seem to be a lot of complicated answers here.. it's really quite simple.. just move the set_db call, it doesn't have to be in your CDBI modules at all..

eg in your main script or handler, before you make any calls to CDBI modules..

my @db_info = get_dbinfo();
My::DBI->set_db('Main', @db_info);
[download]

The Class::DBI documentation covers this. You setup a method called db_Main() which will return a valid DBI handle. All subclasses that don't otherwise override db_Main will use that handle.

FYI, db_Main doesn't work all that well at the moment. The reason is that unless you pass it an Ima::DBI handle (not vanilla DBI) it will have problems with transactions and with automatic setup classes like Class::DBI::mysql. I think Tony posted a code snippet to the mailing list showing how to open an Ima::DBI handle yourself and pass it through to Class::DBI, which is what you should do if you can't use the set_db method.

I wanted to make a Class::DBI object automatically set up by Class::DBI::Pg, but also with mixins of Class::DBI::AsForm and Class::DBI::FromCGI (and CGI qw/:standard/ as per the ::AsForm docs).

I fiddled for a while and when it took too long, just used the Pg part and ditched the other two modules. I had added a method to the object as in the ::AsForm docs, create_or_edit(). But I kept getting an error to the effect that "Person cannot SELECT" and then a bunch of html tags embedded in the SQL! (e.g. tablename and so on).

Probably I should have persevered and maybe improved my understanding of such things, or.. Is this the problem mentioned about using automatic setup modules above? I thought it would be neat to just use these as my base and have an automatic editting script set up, especially since the other modules I found on cpan to do that seemed buggy.

use Mayhem::Config qw/get_config/;

my $base_class_name;

BEGIN {
     my $config = get_config();
     $base_class_name = $config->perl_object_base_class;
     eval "use base '$base_class_name'";
     eval sprintf("__PACKAGE__->set_db('Main', %s);", $config->db_conn
+ect_string);
}
}

1;
[download]