On Thursday 27 November 2008, Oleg Broytmann wrote: > > Or maybe some parameter to the dburi (like backend) would be simpler > > and cleaner. > > Either sqlite2://, sqlite3:// - or sqlite://...?backend=sqlite2.
My preference would be towards the last example using a backend parameter, because that would avoid the need to invent new db scheme names. By using this we can even choose between sqlite1 and 2 (which is again a hardcoded choice if both are installed). Having new db scheme names is probably going to be more complicated, because it would probably imply that we have to define them as distinct backends. Also the backend arg should be just a preference, which should override the default choice of the most recent backend as is done now. I still think that having the default to choose the most recent backend available is still a good strategy, but being able to manually override it using the backend parameter, would give full flexibility to everyone. This way it will still work out of the box, without any change, for people who do not care about the backend, or who only have one installed. -- Dan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
