i would not call this a real versioning as this will not keep track of
which object has been edited.
if you have 10 different ponies and edited pony 3 to 3', you can not
tell that 3' was 3 before. neither can you tell which are the current
ponies, you will only get the last pony with current_pony.
On Oct 27, 4:54 pm, Todd Blanchard wrote:
> Total django noob here. Rails/PHP/WebObjects refugee here.
>
> I'm starting a project where some models need to be fully versioned.
>
> IOW, record update is forbidden - every save to a changed model should
> result in a new record with a new version
Tim Chase wrote:
> Back to the topic on hand, there are several ways to do
> model-versioning. I'm partial to having a FooHistory table that
> mirrors the parent table's fields but has a timestamp associated
> with it. The most recent one is always the Foo object, but
> before a Foo is sav
Is there a big advantage of MartyAlchin Historization over the django-
reversion project?
Has anybody compared the two approaches in detail.
>From what i could understood on the django-revsion site it seems to me
more complete, as it inclueds i.e. file-reversion.
Plus it is easier to use as it is
On Oct 27, 2009, at 6:09 PM, Tim Chase wrote:
>
>> There's quite a learning curve here.
>
> The learning curve doesn't have much to do with Django, but
> rather development in general -- any time you take on a new
> technology (or soup of technologies, in this case Python/HTML/CSS
> Django's tem
> There's quite a learning curve here.
The learning curve doesn't have much to do with Django, but
rather development in general -- any time you take on a new
technology (or soup of technologies, in this case Python/HTML/CSS
Django's templating language, and possibly SQL) there's a hill to
cl
Great, I was trying to decide between that and "The definitive guide"
and guess which one I ordered
Back to Amazon... :-/
There's quite a learning curve here.
-Todd
On Oct 27, 2009, at 5:15 PM, Mike Dewhirst wrote:
>
> Todd Blanchard wrote:
>> Total django noob here. Rails/PHP/Web
Todd Blanchard wrote:
> Total django noob here. Rails/PHP/WebObjects refugee here.
>
> I'm starting a project where some models need to be fully versioned.
>
> IOW, record update is forbidden - every save to a changed model should
> result in a new record with a new version number or timestam
On Tue, Oct 27, 2009 at 1:54 PM, Todd Blanchard wrote:
> I'm starting a project where some models need to be fully versioned.
check django-reversion:
http://code.google.com/p/django-reversion/
--
Javier
--~--~-~--~~~---~--~~
You received this message because y
Total django noob here. Rails/PHP/WebObjects refugee here.
I'm starting a project where some models need to be fully versioned.
IOW, record update is forbidden - every save to a changed model should
result in a new record with a new version number or timestamp along
with identity pulled fro
10 matches
Mail list logo
