Re: Guidance would be most welcome

2006-06-16 Thread Paul Childs
Sweet! Thanks for the heads up. --~--~-~--~~~---~--~~ 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

Re: Guidance would be most welcome

2006-06-15 Thread Waylan Limberg
On 6/13/06, Paul Childs <[EMAIL PROTECTED]> wrote: > > Of course it would be nice just to call the save() and delete() methods > and everything would behave as listed in my first post. > This is one of the Summer of Code projects in the works. You can read about it and offer some input on the dev-

Re: Guidance would be most welcome

2006-06-15 Thread GrumpySimon
Why bother shuffling data between tables? I've got a wiki app I've been working on (slowly - hoping to release soon!), and I add a revision field ( IntegerField ), and just add a new entry with revision+1. The latest version has the latest revision number. Easy :-) Then it's just a matter of som

Re: Guidance would be most welcome

2006-06-15 Thread Carlos Yoder
Hey there Paul. I'm working with a price comparison website, and we have a similar system going on. You see, products have 1+ prices, stored in a prices table. We get prices daily from dealers, and handle historical prices in a different table, just like Waylan said. The prices_hist table holds t

Re: Guidance would be most welcome

2006-06-13 Thread DavidA
I have a similar problem where I want to maintain an audit trail for "manual overrides" to inputs to our risk loop. I haven't implemented it in Django yet, but the way I've done this in the past is similar to Waylan: using a history version of the table. There are a few differences, however. My ta

Re: Guidance would be most welcome

2006-06-13 Thread Paul Childs
Thanks for the input Waylan. It certainly gives me another angle on the solution. I have been digging into the docs again and it seems to me that Django is flexible enough to handle this without having to dive into the source. Of course it would be nice just to call the save() and delete() meth

Re: Guidance would be most welcome

2006-06-13 Thread Waylan Limberg
I have been thinking about how to do something similar - specifically, wikipage history. Note that I have not actually tried any of this yet but I would split the history out into a second table. Perhaps this incomplete example to illustrate: class Page(models.Model): title = models.C

Guidance would be most welcome

2006-06-13 Thread Paul Childs
I have been using Django for about a month now and I just moved over to the development version. I am creating an application in which the client has dictated very stringent database record management in order to have a detailed audit trail on all changes made data. This does not necessarily mean