F
Frank Meulblok
Guest
"but the codebase is littered with DBNAME.TABLE.FIELD phrases, each of which would need visiting in order to fix them." There's a quick & dirty fix for that too: Set up aliases using CREATE ALIAS statements in your startup procedure, to redirect the obsoleted database names to the single remaining connection. Be sure to test though: Since everything goes over a single connection instead of multiple ones, there may be corner cases where concurrency, conguency and transaction flow can change. The bigger headaches will show if the same table names appear in multiple databases, because then you may need to rename tables before you can merge into 1 database.
Continue reading...
Continue reading...