Menu
▾
▴
Re: [Exist-open] Schroedinger's file state
|
From: Christian A. <chr...@ge...> - 2021-04-28 21:20:12
|
Thanks Nick and Jean-Paul. I think I will try this 5.3 update. But ... ... where do I get the 5.3.0 snapshot? I cannot find anything on exist-db.org, only here on docker.com: https://hub.docker.com/layers/existdb/existdb/5.3.0-SNAPSHOT/images/sha256-7192e3988189ff22d0ddc199888619564de457ae604a14eda5ed25eeb9270a3e?context=explore Does it mean I have to go with Docker to update to 5.3? Oh no, so far, I always used the exist-installer-5.2.0.jar to install eXist-db. Thanks and kind regards Christian Am 28.04.21 um 21:26 schrieb Jean-Paul Rehr: > Sorry, it seems my draft email sent off with a hotkey or something. > > As Nick says, this is one of the big bugs in 5.2. The instances I have > still in 5.2 I never rename collections from anywhere - I use remove, > copy, etc in code - just to avoid possible problems. And like Nick, > I've moved over a number of production instances to 5.3 snapshot > without issue for months now. > > JPR > > > > On Wed, Apr 28, 2021 at 8:50 PM Nick Sincaglia <nsi...@nu... > <mailto:nsi...@nu...>> wrote: > > Christian, > This is a known issue that eXist-db 5.3.0 SNAPSHOT fixes. We > also experienced this same issue and it was recommended that we > move to this newer version and we have not had any problems since > doing so. > > Nick > > On 4/28/21 12:55 PM, Christian Achter wrote: >> >> Dear all, >> >> this happened to me now several times during the past half year, >> and on different machines. We are using eXist 5.2.0 on several >> machines (Ubuntu). >> >> Sometimes, when a user renames e.g. an existing >> directory/collection, the renaming works - somehow. The name is >> changed, but the content of the collection is not accessible >> anymore. Re-renaming the collection is not possible. Deleting the >> renamed collection is not possible. >> >> Creating a new collection with the old name is also not possible. >> eXist then reports that this collection already exists (also it >> was renamed). >> >> Our users use Oxygen XML Author to handle our XML files and >> collections. >> >> As an admin, I use the following tools to try to get rid of those >> collections: >> >> * WebDAV (via Oxygen XML Author) >> * eXide in the browser and the file manager you can access from >> there >> * Java Admin Client (bin/client.sh) >> >> All of those do not work. >> >> So in these cases, I have Schroedinger's collections: I can see >> them in the tools mentioned above but I not access them because >> they do not exist anymore. At the same time, I can not delete or >> replace them as they somehow still exist. >> >> Fun fact: I even had XML files I could not access via any of the >> tools above, but they could be accessed by XQuery scripts that >> were exactly reading these files. >> >> Usually, in these cases, I re-install eXist-db and restore a >> current backup. But I am pretty tired of this workaround. >> >> Is this a problem of indexing? How can it be solved? >> >> Thanks for all advise in advance. >> >> Christian >> >> >> >> _______________________________________________ >> Exist-open mailing list >> Exi...@li... <mailto:Exi...@li...> >> https://lists.sourceforge.net/lists/listinfo/exist-open <https://lists.sourceforge.net/lists/listinfo/exist-open> > > -- > Nick Sincaglia > President/Founder > NueMeta, LLC > Digital Media & Technology > Phone: +1-630-303-7035 > nsi...@nu... <mailto:nsi...@nu...> > http://www.nuemeta.com <http://www.nuemeta.com> > Skype: nsincaglia > > _______________________________________________ > Exist-open mailing list > Exi...@li... > <mailto:Exi...@li...> > https://lists.sourceforge.net/lists/listinfo/exist-open > <https://lists.sourceforge.net/lists/listinfo/exist-open> > > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open |
