[Typo3-dev] Versioning Fix

[Mathias Schreiber [wmdb]]

Ingmar Schlecht wrote:
> Mathias and Peter have already modified versioning to work with a 
> separate table, so it's already proved that it's doable.

No.
We DO utilize another table BUT:
We only use it to save the data during the transaction.
We only use ONE table to store ANY versioned records.

Concept:
UID		Holds a UID for identifiing the record
TABLE		what table does the version come from
ORIGUID		original UID of versioned record
VERUID		UID of the record that becomes new "Live" version
ORIGDATA	serialized array with the original data
VERDATA		serialized array with the versioned data

This was a quick fix because we had no time to think about a clever 
concept to do this (clients, clients :))

I don't see much problems with a growing number of records in a table - 
smart indexing might make less trouble.
the seperate table idea means what?
One table for each versionable record?
Hey ho, table inflation :)
I don't like this.
Since performance doesn't really matter in the backend I think one table 
might do the job.

The archiving idea is something more interesting.
What if we keep the data like we do now and supply an archiving cron job 
or standalone script.
This way the admin can decide what and when gets archived.

Suggestions?



-- 
No Subject - No Realname - No Service!
Respect the List/Newsgroup Rules!
  >> http://typo3.org/1438.0.html <<