Hi! > There was a similar thread on this earlier where I commented about a > slightly different way to store the changes: > http://groups.google.com/group/django-users/browse_thread/thread/f36f4e48f9579fff/0d3d64b25f3fd506?q=time_from&rnum=1
Thanks for this one, I already found something usefull. > To summarize, in the past I've used a time_from/time_thru pair of > date/time columns to make it more efficient to retrieve the version of > a row as it looked at a particular point in time. Your design of just > using change_date makes this more difficult. I don't know what you mean exactly, but I'm not using just change_date. The ID in *_history table defines the "revision/version number", so you don't have to use "change_date" to get the exact revision. > I can also think of use cases where I want the versioning to track both > date and time since I would expect multiple changes on the same day. This one is my fault. What I meant was using datetime for that field, for said reasons exactly. Good catch! > Maybe these could also be options? Such ideas are always welcome. I will try and make it as versatile as possible. Regards, Uros --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
