Re: django workaround for multiple primary keys or sqlalchemy

On Mon, Jul 29, 2013 at 10:04 PM, Bill Freeman <ke1g.nh@gmail.com> wrote:
> Its not clear to me whether unique_together will make there be an index, so
> it might be slow.

unique_together implies a multi part index - it's the only way it
could be reasonably implemented.

Cheers

Tom

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.