In MS7 this could have happened (content was not deleted). In Ms8 the
problem should have been solved (since 2001/2/26 12:51:57, MacroImpl.java).
Are you sure, you did use MS8 and is the problem random (as described by
Remy) or reproducible.
In our child store implementations (based on the Tamino DB) we do not
encounter the problem any more.
Best regards
Juergen Pill
-----Original Message-----
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 09, 2001 2:58 AM
To: [EMAIL PROTECTED]
Subject: Re: Current stability of M8
> I'd like to know what is the level of stability of the
> current slide release (M8).
As a whole, it's not feature complete, so it can be considered alpha
software.
> Also, when moving files between two collections, the files
> are logically moved from one collection to the other. But
> physically on disk, the source file remains there.
>
> So when one try to put the same file name in the source
> collection, we get an error because the file is present on disk.
>
> Is this a correct behavior? do we have to explicitly delete
> the file after a move command?
I've reproduced that problem using the file content store. It appears to be
quite random, and it could come from file locking issues.
The JDBC content store seems to run fine.
Remy
