This database column 'version' is not for versioning (as in WEBDav or
similar things), it's Hibernate special column used to detect optimistic
locking failures. So the previous version is not stored anywhere.
BTW, this column exists in many tables in AtLeap. I doubt that it can be
used for other purposes.
To implement versioning you could probably reimplement our methods for
updating content field value (those found in ContentFieldValueDAO and
ContentFieldManager) to add new record to DB instead of modifying
existing. But you will also (at least) need to modify logic in classes
that access CFVs (for instance, finders in ContentFieldValueDAO, maybe
tags like ContentTag).
Of course, here you will need some column to be added to CFV which will
store version number, this column will probably need to be added to
CFV's business key (which is currently <localizable owner, field
identifier, locale>). If you will not modify CFVs at all, existing
'version' could be dropped.
jeff gerbracht writes:
> I notice that the most recent version of fields are stored in the database,
> al_core_field_value. This table has a version number but I don't see
> anywhere where the previous versions are stored. Are the previous versions
> stored elsewhere?? If not, I'm hoping that I can fairly easily modify
> atleap to do an insert instead of an update statement to keep these previous
> edits around.
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
users-unsubscribe@...
For additional commands, e-mail:
users-help@...
