On 10/31/07, George Vilches <[EMAIL PROTECTED]> wrote: > Or (I just saw your follow-up e-mail), is all of this a moot point since > something like this is going to be made totally invalid in the future? >
That's it. Targeting a non-unique column in a ForeignKey field is invalid. It's invalid now, and will continue to be invalid. The difference is that it's not caught and flagged as an error now, and will be when queryset-refactor gets merged into trunk. If you can whittle down your real problem to an example that does not include this kind of invalid relationship (you said you are actually using OneToOne fields?) maybe we could make some progress on understanding/solving the real issue you are facing. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
