Hey Uros,
Just two weeks ago, I've been trying to make my own generic history
implementation, but then decided for lack of time, to just make a
one-shot implementation and wait for someone else to write a clean
implementation. Awesome you're already working on it.
To help you find an optimal des
Uros Trebec wrote:
> > Sounds nice, this is a feature I'm currently looking for... but I've
> > already started my own implementation.
>
> Nice! Do you have anyting in code yet? Any bottlenecks?
>
sorry not yet. But will come, I need it for my current development.
>
> > I would just share it wit
Uros Trebec wrote:
>
> > 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 do
> > It would be nice to record "who" made the change (optionally when there
> > is a user with an id available).
>
> I was thinking of not pushing the use of such fields, because there is
> no easy way to figure out how each applications handles
> accounts/users.
and
> > I'd also like an automat
On 6/19/06, IanSparks <[EMAIL PROTECTED]> wrote:
> Although you have a date field in your example model it might not hurt
> to add an automatic timestamp to a model that uses versioning in this
> way.
Changing the versioned model because of use of versioning is something
I would like to avoid. F
Hi!
> Great to see that your RFC is pretty much exactly what I was thinking
> (feature and implementation-wise) when I posted
> http://roups.google.com/group/django-developers/browse_thread/thread/d90001b1d043253e/77d36caaf8cfb071
I'm glad! Thanks for the link too.
> It would be nice to record
> Sounds nice, this is a feature I'm currently looking for... but I've
> already started my own implementation.
Nice! Do you have anyting in code yet? Any bottlenecks?
> I would just share it with you.
>
> I've build a single table History with :
> - "change"; a text field which will contain a
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
Uros Trebec wrote:
> 2.1. Basic models:
> To enable history tracking Bob has to create a sub-class for those
> models that he will like to track:
>
> class Post(models.Model):
> author = models.CharField(maxlength=100)
> title = models.CharField(maxlength=100)
>
Uros Trebec wrote:
> class Post(models.Model):
> author = models.CharField(maxlength=100)
> title = models.CharField(maxlength=100)
> content = models.TextField()
> date = models.dateField()
hi,
sorry to jump in so late into the discu
On Sat, 2006-06-17 at 07:27 +, william wrote:
>
[...]
> Sounds nice, this is a feature I'm currently looking for... but I've
> already started my own implementation.
>
> I would just share it with you.
>
> I've build a single table History with :
> - "change"; a text field which will conta
Hi Uros,
Great to see that your RFC is pretty much exactly what I was thinking
(feature and implementation-wise) when I posted
http://groups.google.com/group/django-developers/browse_thread/thread/d90001b1d043253e/77d36caaf8cfb071
It would be nice to record "who" made the change (optionally when
On 6/17/06, Vitaliy Fuks <[EMAIL PROTECTED]> wrote:
> It would be nice to record "who" made the change (optionally when there
> is a user with an id available).
+1
> I thought that storing complete row copies on both inserts and updates
> to original object isn't that bad - it certainly simplifi
Uros Trebec wrote:
> Hi, everyone!
>
> First: introduction. My name is Uros Trebec and I was lucky enough to
> be
> selected to implement my idea of "history tracking" in Django. I guess
> at least some of you think this is a very nice feature to have in web
> framework, so I would like to thank
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
To summarize, in the past I've used a time_from/time_thru pair of
On 6/14/06, Uros Trebec <[EMAIL PROTECTED]> wrote:
>
> 2.1. Basic models:
> To enable history tracking Bob has to create a sub-class for those
> models that he will like to track:
>
> class Post(models.Model):
> author = models.CharField(maxlength=100)
> tit
16 matches
Mail list logo
