Thanks Alex and Emmanuel for the quick and valuable help! We will have a look at the change log if we can get some ideas from that!
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Karasulu Sent: Wednesday, July 09, 2008 4:10 PM To: [email protected]; [EMAIL PROTECTED] Subject: Re: Transaction for interceptor There's still a lot to do. The default change log as it is implemented today is not fully capable of providing what is needed in production and is devised just for rollbacks in our tests. It's definitely a good start though - thanks for pointing it out. Alex On Wed, Jul 9, 2008 at 10:05 AM, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > Tanja Ertl wrote: > >> Hi Emmanuel, >> >> would a Stored Procedure provide me with such a transactional behaviour? >> Reading fast over the document I would guess not. >> >> > In combinaisson with the ChangeLog service, yes. The changeLog interceptor > stores a revert operation for each modification done, associated with a > unique id. If the operation fails, you can revert to a specific id (like in > subversion). > > This is how we handle the tests for the server : instead of starting a new > instance of the server for each test (wich is a costly operation when you > have hundred of tests), we revert the previous modifications done by the > previous test, and restore the server back to its initial state. > > I'm pretty sure that it could fit your need. Here is some documentation > about the changeLog feature : > > http://directory.apache.org/apacheds/1.5/versioning-and-snapshots.html > > > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com > directory.apache.org > > >
