Ja - that was going to be my next step - bit stretched for time at the moment - so was just a quick email to see if anyone had any thoughts.
I think even if it was a problem with MySQL - an error should have been raised somewhere. Either way - I'll build a test for it and let you know the results. Thx Cal On Mon, Oct 3, 2011 at 7:52 PM, Christophe Pettus <x...@thebuild.com> wrote: > > On Oct 3, 2011, at 11:31 AM, Cal Leeming [Simplicity Media Ltd] wrote: > > > I can provide exact further info, but this was just a preliminary email > to see if this was expected behavior - or actually a bug?? > > You might try capturing the generated SQL and running it on a command line > against the DB to see if the problem is in MySQL, or in the Django backend. > > -- > -- Christophe Pettus > x...@thebuild.com > > -- > 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. > > -- 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.
