On Sat, Mar 14, 2009 at 8:35 AM, koenb <koen.bierm...@werk.belgie.be> wrote:
> > > Is there any downside to checking this in immediately? It's a simple > > enough change that I don't see it introducing any bugs (famous last > > words, right?)... > > Please don't allow using connections from different database backends > unless the problems of using the correct database options are resolved > first. Both model fields and query creation still have a lot of uses > of the 'default' connection to get to these options. This implies that > there is a possibility to get hard to debug weird sql trouble when > mixing database engines. > Enforcing the same backend for the different connections might be a > good idea for now. > > Koen > > > How is that any different from the present scenario if one assigns to query.query.connection? Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
