[CPS-devel] Altering existing documents

[Jean-Marc Orliaguet]

sebmas wrote:
> M.-A. DARCHE a écrit :
>> sebmas a écrit :
>>  
>>> After a few years of intensive CPS using, our ZODB has grown and is
>>> about 10GB big. So packing is sometimes difficult ("Data.fs" and
>>> "Data.fs.old" fill the filesystem together) and I think it's not 
>>> sane to
>>> have such a big database.
>>> Why is it so big ? Full of attached files, images, ...
>>>
>>>     
>>
>> Packing is needed but there are other things to purge regularly
>> than just the old transactions :
>>
>> 1. Purging the localroles of deleted members
>> 2. Purging the repository to remove orphan documents
>> 3. Purging old archived revisions of documents
>>
>> The cpshousekeeping script does the two first tasks :
>> http://svn.nuxeo.org/trac/pub/browser/CPS3/products/CPSUtil/trunk/bin/cpshousekeeping 
>>
>>
>> The third task can be done through the ZMI
>> -> portal_repostory -> Get details
>>
>>
>> Cheers,
>>
>>   
> I'm already doing this, but some sections of our site have become 
> download areas, providing more and more huge files (I just refused to 
> increase the filesize limit so that ISO images could be added).
> Moreover, some existing documents should be updated in order to take 
> layout and schemas changes into account (fields added, removed, 
> replaced by custom ones, new default values, ...)
> I'll have to provide custom document types, mostly based on Flexible 
> architecture, and I'm pretty sure that their structure will change 
> many times.
> I can change the schemas/layouts to solve these "problems" for any 
> forthcoming document, but how to deal with the existing ones ? I can't 
> ask users to delete and recreate their work each time !
> But I've no idea how to perform this ...

The layout information could be read from portal_layouts even for 
flexible layouts. I'm not sure why in the current implementation layout 
definitions are persisted.

/JM