Re: [las_users] multiple MySQL drivers

[Jonathan Callahan <Jonathan.S.Callahan@xxxxxxxx>]

Jerome,

I don't see why you shouldn't be able to have multiple drivers.  Just for clarification, when we talk about a database 'driver', we're referring to a perl module that inherits from TMAP::DBI and deals with the specifics of some new database.

For each driver you must have a separte driver.pm file and each driver must be mentioned in the insitu.pl file in the same way as the other drivers.  Then each dataset configuration file must mention it's own specific driver in the <database_access> properties.

If, instead, what you've done is just put your data into separate MySQL databases then you don't need different drivers at all.  Just refer to the appropraite database and table in the <database_access> properties.

I can't think of any reason why this shouldn't work.

Please clarify further if I've misunderstood what you're doing.


-- Jon


Jerome King wrote:

Hi all,

I have 4 LAS set up to talk to 4 different MySQL databases.

I am now working into grouping those 4 LAS into ONE LAS. Therefore this ONE LAS will talk to 4 MySQL databases.
Since I wrote a different driver for each MySQL databases, I would like to just refer those drivers in the insitu.pl instead of writing ONE driver that would work for all 4 databases.

I refered them as "mysql1", "mysql2", "mysql3",...but of course this did not work since the insitu.pl calls the module DBD/mysql.pm and there are no DBD::mysql1 module, DBD::mysql2 module,....

I was wondering if there was a way to do this so I don't have to write a driver that encompasses all 4 mini MySQL drivers.

Thanks,
Jerome