nielsene wrote:Along the same lines as the format conversion you listed, various replication strategies could also require switching or mutliple drivers.
Some testing strategies could require intercepting the flow to the database at different points and subsituting a different database, possibly even a different driver.
You might have some sort of failover strategy that would requiring changing from your Oracle DB to a backup PostGreSQL; if keeping a homogenous cluster was either too inexpensive or deemed too great a risk, etc.
Albeit all of these are rather "out-there', but....
I was thinking of implementing a
dynamically
loadable
driver, but the fact is, the most obvious...(data store conversion) could be done without the over head of DLD, by simply storing data in a temp session like:
1) Script start, Open connection, (SELECT *) and store results in array
2) Serialize array, Script complete
3) Script start, Open connection, Unserialize array and store native array in new data store.
The functionality is still available and easy enough to implement, but you don't need the over head of DLD connecting "dynamically" to a data store...seeing how this operation is quite frequent as opposed to data store conversion, it makes sense to keep the binding static.
Opinions, Arguments, etc...?
Cheers
