On Thu, 2008-12-18 at 15:14 +0100, Hallvard B Furuseth wrote:
Wel, if you copy first and increment after, you can't use the 'unique' overlay to prevent HEAD from having same version as a versioned entry. But if that doesn't worry you, then yes that'd be simpler.
You're right ... However,I see an alternative pattern :
increment version number THEN copy to versionned DNR and leave as is.
unversionned RDN/HEAD is always 'current', version number in HEAD points to the last saved version
versionnable entity can have a container for uniqueness but this could be enforced by the algo, my directory is not writable by users it's an application back end.
LP
Lorenzo Pastrana - Happy End Vision -------------------------- Design web Conception multimédia Communication visuelle et édition -------------------------- Tél. : 01 42 47 83 09 Fax : 01 47 70 70 19 E-mail : lorenzo.pastrana@happyend.fr
