On 1/31/06, Luke Plant <[EMAIL PROTECTED]> wrote: > The Django ORM basically assumes a third normal form database design. > It half enforces this by adding a primary key to every table (if you > don't specify one yourself), and only allows one field to be a primary > key in the class definition. However, there is nothing to stop you > adding other constraints (using unique_together or directly on the > database), and effectively using that as your primary key. The > automatic primary key is needed for things like the admin interface to > work i.e. you need a simple way of being able to specify an object to > delete.
Nice explanation, Luke! I've added it to the FAQ. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
