You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to eXist-db's lack of ACID transactions semantics, the cause of the above error, as with any error that occurs whilst storing an XML document in eXist-db, will corrupt the database!
The reproducible Test Case is simple:
declarevariable $collection-conf := document {
<collection xmlns="http://exist-db.org/collection-config/1.0">
<index xmlns:int="http://services.parallelgraphics.com/vm/mmr/vm-interactivity-xml/all">
<!-- Range index -->
<create qname="entry"type="xs:string"/>
</index>
</collection>
};
(: Create Collection, and store the Index config :)xmldb:create-collection("/db", "test"),
xmldb:create-collection("/db/system/config/db", "test"),
xmldb:store("/db/system/config/db/test", "collection.xconf", $collection-conf),
(: Store the Document :)xmldb:store-files-from-pattern(
"/db/test",
"/tmp",
"test1.xml",
(),
fn:true()
)
The test1.xml document needed by the above query has the content:
<entry>something<![CDATA[Item]]></entry>
I have tested this with eXist-db 7.0.0-SNAPSHOT. I have not yet checked older versions of eXist-db, but having taken a quick look at the Git history, I believe this bug has been hiding for a very long time, and so will likely be present in at least 4.0.0 onwards.
The text was updated successfully, but these errors were encountered:
It is not possible to store a document into eXist-db if the following two concerns align:
Attempting this will cause an error like this:
Due to eXist-db's lack of ACID transactions semantics, the cause of the above error, as with any error that occurs whilst storing an XML document in eXist-db, will corrupt the database!
The reproducible Test Case is simple:
The
test1.xml
document needed by the above query has the content:I have tested this with eXist-db 7.0.0-SNAPSHOT. I have not yet checked older versions of eXist-db, but having taken a quick look at the Git history, I believe this bug has been hiding for a very long time, and so will likely be present in at least 4.0.0 onwards.
The text was updated successfully, but these errors were encountered: