On Aug 13, 11:18 am, Steven Davidson <[email protected]> wrote: > > It would have to be another datetime field rather than an is_current flag > > because an is_current flag wouldn't help me for queries in the past (if that > > makes sense). > > Ah yes, of course, I had not fully grasped that bit. A nullable foreign key > reference to the State that supersedes it might come in useful in future, > and avoids adding another pesky date field. But thinking about it some more > it would probably make the ORM query a little more involved.
I actually like that idea. Like a linked list. It would mean the django query could be simpler, and the post processing wouldn't be too bad. -- 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.
