Possible documentation/implementation bug for unique_together

[puff]

I'm relatively new to Django and used unique_together in 1.5 per the development documentation:

unique_together = ("driver", "restaurant")

This appears to cause run time errors leading to a transaction abort.  However, 

unique_together = ("driver", "restaurant",)

seems to work.

Is this a documentation bug or implementation bug?  If so how to determine which and best report it?

Regards,

Richard

[Thomas Orozco]

Those two tuples are stricly equivalent from Python's point of view, so the problem must be somewhere else,

Did you change anything else? What's the error message like?

Cheers, 

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/dd8fef08-4486-4827-af62-fc92604aafcb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.