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).

2. Leave [4610] in, and not allow forward references in MySQL.

I'd suggest #1 for orthogonality, but does anyone else have any ideas?

Jacob

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to