Ramiro Morales wrote:
> Well that´s, nothing more nothing less, the expected behaviour: > > http://www.djangoproject.com/documentation/model_api/#unique-together I guess I must have read the description wrong (I still don't see how the description implies that a NULL field gets ignored or whatever). > What happens if you try > > unique_together = (('book', 'chapter', 'from_verse'), > ('book', 'chapter', 'from_verse', 'to_verse',)) > So I tried this, but now, after entering Genesis 1:1-2, I can not enter anything that has Genesis 1:1 in it. So, Genesis 1:1 is "not unique" apparently, either. Thanks! Seemant > > Of course yo should zap the DB and make manage.py re-create if from > scratch from the models (so the additional UNIQUE constraint is set) > before testing > this. Yes, rm'd the db and re-syncdb'd it :) Thanks again! Seemant --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
