On Tue, 2008-09-16 at 08:57 -0700, meppum wrote: > Thanks Malcolm. The only way I can think to get around this is to > create a unique constraint between those two columns during syncdb. Is > there a less disjointed way of accomplishing the same thing?
You're really wanting to introduce some extra constraint at the database level. So do it at that level, such as by adding something that is called as part of the syncdb signal to set up a constraint or trigger or something appropriate for your database. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
