On Fri, Mar 25, 2011 at 11:41 PM, Jacob Kaplan-Moss <ja...@jacobian.org>wrote:
> On Fri, Mar 25, 2011 at 6:45 PM, maxi <maxiroba...@gmail.com> wrote: > > Yes, that seems to be the problem. Firebird doesn't support deferred > > constraints. > > Are there any approach or workaround to solve this ? > > No workarounds, no. We need to refactor our test suite to not rely on > deferred constraints (except of course where we're actually testing > deferred constraints, and there we need to skip those tests on less > intelligent DBs). Most of the time we should just be able to rewrite > our test data to not require forward references; where we can't we > need to switch out fixtures for setup/teardown methods. > > Is there a ticket open to track this task? If not I'll open one. > > Jacob > > -- > 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. > > There's http://code.djangoproject.com/ticket/3615, most of the effort there has been on making MySQL not be stupid though :) Someone at PyCon told me they found a way to make it work though (Chris Adams I think?). Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing 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.