Perhaps someone could figure out how to extend the DBI into a sub-module that abstracted the database issue? It could check for environmentals and depending on what it found, execute the database-specific code from there... it would be only sort of non-portable then, kind of like DBD::xxx ... hmmm... too early, should probably drink some coffee before I go spouting off like this. =P
In reply to Re: Checking installed MySQL databases with DBI
by Dragonfly
in thread Checking installed MySQL databases with DBI
by fpi
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |