Christophe Combelles a écrit :
Racinet Georges a écrit :

On May 12, 2009, at 5:40 PM, Christophe Combelles wrote:

Thanks, I've finally backported some fixes for StorageAdapter, which was overwriting too many fields during a document update.

There is a remaining bug with DiskFile, even on CPS 3.4.8.

- change the File schema to use DiskFile
- create a File objet in the workspace, and attach a file
- publish the file in a section
- change the filename of the Diskfile in the workspace

-> the filename is changed in the section as well, although it should not.

Additional informations:

If the filename is changed a second time, cloning occurs and the filename doesn't change in the section. If I change the description instead of the filename, the problem does not occur and the file is cloned correctly.

Christophe



Wow, I remember those fixes, one of the last generic work on CPS I've done as a Nuxeo employee, The primary goal was to avoid useless writes in LDAP backing directories, while still being able to update a meta directory upstairs (for CPS specific fields that would be stored in another - ZODB - backing).

Did you backport this on your project for directories or documents ? I've always wondered what the overall (positive, I hope) performance impact in the case of documents would be, and never had a chance to measure that. Any numbers to share ?

I've backported it for CPSDocuments, to avoid dataloss with DiskFile objects overwriting an already published file. This is not related to performance so I didn't measure anything.



Cheers,

--
Georges Racinet, http://www.racinet.fr
Zope/CPS/Plone expertise, assistance & development
GPG: 0x4862FFF7







_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel



_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

Reply via email to