[Typo3-dev] Initiating a page version feature

[Michael Zedeler]

Peter Niederlag wrote:

>>>Since there is a group working on a database abstraction layer, this
>>>definately belongs there.
>>
>>I agree, and I guess this group (mostly me) is looking for some people
>>to join the group and start discussing. Maybe Kitzbuehl would be a
>>chance to have kick-off meeting.
> 
> 
> Excuse me, but can you explain why versioning of pages/Content requires
> DB-abstraction?

Well it isn't *required*. Anything can be done without extra abstraction 
layers. The question is: "is it good design?". I don't think so.

> Since other DBM-Systems allow versioning "in itself"?

I think there is two options here:

Option 1:
Typo3 is already pretty much married to mysql, so if it supports 
versioning one could consider to use that feature. I don't think it does 
support versioning, but I am not that up to date with latest mysql 
developments.

This option may be the only viable option since introducing a (opaque) 
database abstration layer will take very long time (a quick and dirty 
count in the source code yields 852 direct calls to mysql from php files 
in the typo3 3.5.0 distribution). Especially if other developers keeps 
adding features that introduces new database-abstraction-incompatible 
dependencies (such as versioning!).

(And then we junk or postpone the database abstraction layer. The 
database abstraction group might have a different view, though.)

Option 2 (my preference by far):
Put it in the database abstraction layer. Things stored in the database 
shouldn't worry about their own version unless it is needed. Likewise 
for the code that uses them.

M.