On Dec 18, 9:50 am, Alex Gaynor <alex.gay...@gmail.com> wrote: > I'm wondering if perhaps the most prudent thing to do would be to > simply remove this check. The end result will be you'll get an > integrity error on Postgres/Oracle when you try to save (and SQLite > and MySQL will just let you do whatever).
That would certainly work for us. I guess it's really a question of how it'd affect users with multiple truly distinct databases. I think it's a nice error for people "new" to Django and the concept of multiple databases, but when you're using more than one DB already... Brett -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
