version has tons of things locked
I was doing a bunch of changes in a version and saved the version without any problems. But now tons of things are claiming to be version locked. It seems that if I go into the version, make a change, save the version and the leave the version, that object won't be locked anymore. The problem here is that they may be about 1,000 objects that are version locked. How can I fix this? The objects that are locked should not have been locked, so if I can throw out all of the crud that's messing things up, then it should be fine. (Yes I'll make a backup of the db before I do anything.) What are my options here? At one point a new Python Script that was created in the version ended up not being able to be accessed outside of the version. I made a copy of it and then got POSkey error exceptions. I copied the contents locally, deleted the original, recreated it and pasted the old contents back into it. Everything is fine for that script now. What would have wigged out the version? Any help is appreciated. Thanks, -Chris
Ok. So I think I fixed it, but this makes no sense. I packed the database to 0 days and then went to the version management thinger in the Control Panel. Saved the version, and all of the version locks have gone away now. Why did they not show up before? What does packing have to do with it? If I continue to use versions, am I going to run into this problem again? -Chris On Wed, 13 Nov 2002 15:16:51 -0500, Christopher N. Deckard spoke forth:
I was doing a bunch of changes in a version and saved the version without any problems. But now tons of things are claiming to be version locked. It seems that if I go into the version, make a change, save the version and the leave the version, that object won't be locked anymore. The problem here is that they may be about 1,000 objects that are version locked. How can I fix this? The objects that are locked should not have been locked, so if I can throw out all of the crud that's messing things up, then it should be fine. (Yes I'll make a backup of the db before I do anything.)
What are my options here? At one point a new Python Script that was created in the version ended up not being able to be accessed outside of the version. I made a copy of it and then got POSkey error exceptions. I copied the contents locally, deleted the original, recreated it and pasted the old contents back into it. Everything is fine for that script now. What would have wigged out the version?
Any help is appreciated.
Thanks, -Chris
Christopher N. Deckard wrote:
won't be locked anymore. The problem here is that they may be about 1,000 objects that are version locked. How can I fix this? The objects that are locked should not have been locked,
Objects only become locked if you modify them in the version. What changes have you made?
What are my options here?
Commit the version, in which case all changes made in it will be committed to your ZODB. Abort the version, in which case all changes made in it will be lost.
At one point a new Python Script that was created in the version ended up not being able to be accessed outside of the version.
That's exactly what should happen.
I made a copy of it and then got POSkey error exceptions.
if you get those, it might be time to ask on zodb-dev@zope.org.
Everything is fine for that script now. What would have wigged out the version?
Versions are pretty old and crufty, as a rule of thumb, don't use them. cheers Chris
On Thu, 14 Nov 2002 11:36:50 +0000, Chris Withers spoke forth:
Christopher N. Deckard wrote:
won't be locked anymore. The problem here is that they may be about 1,000 objects that are version locked. How can I fix this? The objects that are locked should not have been locked,
Objects only become locked if you modify them in the version. What changes have you made?
I created folders inside existing folders (maybe about 800 new folders). I added 5 new Page Templates in various places. Edited some others. Added 5-10 new Python Scripts, edited some others.
What are my options here?
Commit the version, in which case all changes made in it will be committed to your ZODB.
I did that. But things continued to be locked by the version. I had to make a new transaction to modify an object before I could save the version. At that point it would actually become unlocked.
Abort the version, in which case all changes made in it will be lost.
You can't abort a version when the version claims that there is nothing to abort.
At one point a new Python Script that was created in the version ended up not being able to be accessed outside of the version.
That's exactly what should happen.
That shouldn't happen if the version was saved. I think you missed that part about me actually saving the version.
I made a copy of it and then got POSkey error exceptions.
if you get those, it might be time to ask on zodb-dev@zope.org.
Ok. Will do.
Everything is fine for that script now. What would have wigged out the version?
Versions are pretty old and crufty, as a rule of thumb, don't use them.
I've never had this problem with versions and I've been using them for well over a year. If versions are that bad, maybe they should be deprecated until a new version of versions comes around.
cheers
Where's my eggnog?
Chris
That's my name. :-) Thanks, -Chris
participants (2)
-
Chris Withers -
Christopher N. Deckard