Hi Doug, On 4/26/07, Doug Van Horn <[EMAIL PROTECTED]> wrote: > [Links] > There's no harm in having unique columns in addition to your primary > key (as you describe). The nut of the problem around natural keys, > IMHO, is that the rules that make them natural keys today can change > such that they are no longer keys tomorrow. When that happens, you > float your resume and find a new gig.
Thanks for the links. :-) In my case, the primary_key will ever be unique. It is impossible that another entry has the same name. > Don't take my recommendation as authoritative. I'm not a DBA by > trade, I'm a code monkey. Take the time to read up on the subject. > The Wikipedia pages are a good start. :-) Yes, I'm a code monkey too and I prefer giving the db design to something else. :-) > doug. Thanks again Kai --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
