Actually, thinking about this thread(and other one which needs something similar), i think the best way is not to confuse the 'history/update' with the actual 'data'; i mean, that history/updates are just for tracking the revisions, the individual attributes of the entity should be present in the parent table; and only this parent table should be referred for any 'top' or 'recent' data, as it in its entirety contains the 'present' state of things.
If at all you have to show the revisions/updates/history of the data, then with the pk from the parent table, query the history table and show the records. -V -- 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.
