Quoting Nick Kew <[EMAIL PROTECTED]>:
Well, that's an option. But wouldn't it perhaps be more elegant to use a container? <DBDConnection alias> DBDriver foo DBDParams "......" etc </DBDConnection>And if the container is optional, we have back-compatibility for free.
Nice one. Never crossed my mind...
That's fine. Or it could just be an apr array, on the premise that it's not going to grow so big as to make linear lookup a problem.
Yeah, it could. I'm guessing people will have a few of these per VH at the most.
AFAICS only dbd_open and dbd_[c]acquire would require an extra arg. But back-compatibility at the API level would be a Good Thing.
Wouldn't ap_dbd_prepare also need to know which database connection to pick? -- Bojan
