Hallöchen!
Dan writes:
> [...]
>
> I don't think it's best practice to give meaningful names to
> primary key field in Django, you should probably have field name
> and let Django auto-create a id field.
You're right. I now also think that Django's abstraction layer for
the RDBMS -- albeit thin -- means that you're better off with
unique=True fields in all cases. The common advantages of primary
keys are mimicked by Django very well.
I only hope that InnoDB's lookup works for unique=True fields as
fast as for primary_key=True fields ... ;-)
Tschö,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
