see here
http://djangopackages.com/grids/g/versioning/
ore there is also a interesting chapter on versioning on page 263 here:
http://books.google.com/books?id=lJwOcsZq5g4C&printsec=frontcover&dq=django+pro&hl=de&ei=TdA-TdSyH4GA4Aat1fGwCg&sa=X&oi=book_result&ct=book-thumbnail&resnum=1&ved=0CCwQ6w
On Jan 25, 12:08 pm, Juergen Schackmann
wrote:
> why do you want to create the dual tables, instead of only having one table
> with a current tag that holds the old version and the current ones? and then
> handle access to those via different managers?
> have you also had a look at the available v
why do you want to create the dual tables, instead of only having one table
with a current tag that holds the old version and the current ones? and then
handle access to those via different managers?
have you also had a look at the available versioning apps?
--
You received this message because
You probably want to look at abstract models in Django. It's also known as
concrete inheritance in some ORMs
--
Jani Tiainen
On Tuesday 25 January 2011 09:42:08 akaariai wrote:
> Hello all,
>
> My problem is as follows: I have content (for simplicity, lets say
> articles), and some content re
Hello all,
My problem is as follows: I have content (for simplicity, lets say
articles), and some content related to that (authors for the example).
I would like to add the ability for users to create versions of the
content. The procedure from user perspective is as follows: they click
a button (
5 matches
Mail list logo
