On Thu, 2005-12-15 at 14:24 -0800, Kevin Brown wrote: > Geo Carncross wrote: > > I know we talked about this earlier, but I think for 2.2 we need to make > > it possible to have multiple queries- we talked about it per database > > layer, but why not a global conformance level setting? > > > > DB_CAN_VIEW > > DB_CAN_TRIGGER > > DB_CAN_SUBSELECT > > DB_CAN_FOREIGNKEY > > (etc) > > > > and select the appropriate query at that point? > > Hmm...if you're going to do that, perhaps it would be better to just > put the queries and the immediate logic that goes around them into the > db-specific code files. Then it's a matter of making the proper > function calls from the db-independent code.
That's what had been originally proposed, but there are a number of problems with it: * It has to be done all at once, or someone will complain it looks ugly * It's harder to test all backends equally * It would be a lot of work * Nobody wanted to do it :) With this idea, it can be implemented incrementally, which is good, because there are (presently?) only a few queries like this. Any DB could then "step down" their conformance setting to check out the performance of the other queries with their database. > Might be more work keeping things synchronized as development > proceeds, but you'd be able to use all the capabilities of whatever > backend you're talking to without fear. In fact, if you did this > right, you could make the backend representation at the table level > completely different between databases if that proved to be > advantageous. I like that last part, but I'm hoping for something to keep 2.2 compatible with 2.0... -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/
