i do know the circumstances: copying a Data.fs into a ZEO server that was not shut down while this copy operation took place. i'll have to surprise you on the explanation. i did not dig it out. i did not have time for that, and i don't have time for it now. the effort to do the right thing and simply stop ZEO for this copy operation was much smaller than trying to figure out where the "problem" is. i don't even consider it a "problem". even you should realize that there is no database that allows you to just replace its filesystem data "on the fly" without the application's knowledge. IMHO there is no problem in saying "just don't do it, stop ZEO before copying a new Data.fs into it" and that's the end of it. jens On Thursday, May 23, 2002, at 01:18 , Chris Withers wrote:
Jens Vagelpohl wrote:
i don't know. i have seen it happen. that's all.
Don't cop out like that ;-)
If you've seen it happen, then you must at least know the circumstances, and I'd be surprised if you hadn't dug out an explanation...
cheers,
Chris