On Sat, Aug 29, 2009 at 7:51 PM, ckar...@googlemail.com<ckar...@googlemail.com> wrote: > > Really no ideas? > > Chris >
Is there any way you could define a stable ordering for the SinglePoint model? You could ensure that the "smaller" SinglePoint gets stored in p1 and the "bigger" SinglePoint in p2 in a custom save method. If that isn't an option, you might want to implement a check in your save method. I don't know how you could implement a database UNIQUE index which would reject reversed relationships. Matthias -- FeinCMS Django CMS building toolkit: http://spinlock.ch/pub/feincms/ --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
