Ah, I see. Thanks for all the info. So there is no way to clean up cluster revisions? I currently don't have the time commitment to create the backup scripts with consistency checking (but would like to do this in the future).
Will exporting and importing achieve what I want to do? Is everything exported properly into XML? -mike > -----Original Message----- > From: Alexander Klimetschek [mailto:[email protected]] > Sent: Tuesday, February 09, 2010 5:45 AM > To: [email protected] > Subject: Re: Revision cleanup > > Michael, > > On Tue, Feb 9, 2010 at 11:38, Alexander Klimetschek <[email protected]> > wrote: > > What Guo meant is to delete the table that holds the (virtual) > version > > workspace, defined under <Versioning> in the repository.xml. The > name > > of that db table depends on the config (mainly schemaObjectPrefix). > > AFAIK that approach should work, however make sure you make backups > > before trying that! > > Reading your original post again, it sounds like you only mean cluster > revisions. To repeat, those revisions are not related to JCR versions, > ie. JCR versions are stored just as any other nodes, only in a > different persistence manager = "virtual" workspace. The cluster > journal works a layer deeper. > > So Ian's description should quite hit the nail for you. > > Regards, > Alex > > -- > Alexander Klimetschek > [email protected]
