On Tue, Oct 6, 2009 at 9:15 PM, Robert Field <rcf_program...@yahoo.com>wrote:
> > On Oct 6, 10:09 am, Karen Tracey <kmtra...@gmail.com> wrote: > > > > Personally I'd look pretty closely at the need to store a value dependent > on > > the primary key in some other field of the model. Is this really > absolutely > > necessary? > > > > Karen > > > In relational models it's pretty standard to use the primary key as > the lookup in other tables. > > One reason is that it's the unchanging way of identifying a row. > Names, addresses, and the like, all change. The row and its ID number > stay the same. > > Yes, everything you say is true. But I am not sure what it has to do with what was being discussed here, which was having a 2nd field in the very same model instance with a value that depends on the value of the instance's primary key field. That is, a column in the table where the value for a particular row is somehow dependent on the row's primary key value. That is what I was saying I'd look closely at the need for. Karen --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
