On 2/28/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > On 2/27/07, Seattle Daniel <[EMAIL PROTECTED]> wrote: > > As I read it, there is not a way to force InnoDB to check constraints > > at commit. And once there is it will be quite some time before the > > mass of MySQL instances support it. > > So... I think that leaves is with two kinda sucky choices: > > 1. Revert [4610] so that all databases work the same way, and not > allow forward references in serializers (or elsewhere).
I'm -1 on this. Serialization and fixtures are near useless if you can't do forward references. [4610] introduces a test for forward references, and fixes a problem with Postgres. [4610] doesn't introduce any new functionality or break an existing implementation for MySQL - it just introduces a test that reveals a problem that has always been there. > 2. Leave [4610] in, and not allow forward references in MySQL. If there is no potential for a genuine fix for MySQL, this would be my preferred option. Reverting [4610] only serves to break Postgres; it won't return MySQL to working status. MySQL has never allowed forward references. We just didn't have a test that revealed the problem. An intermediate option would be to revert/comment out the test as an interim measure. This is the 'head in the sand' approach, but it would let the test suite pass for MySQL. Either way, the problem/limitations with MySQL needs to be mentioned in the documentation (both serialization and fixtures). Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
