use of atomdb:edit-path-info() causes cardinality issues
Closed this issue · 1 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. under some circumstances, use of atomdb:edit-path-info() will result in
strange cardinality errors, probably due to eXist's use of storing some
temporary fragments in the database
What is the expected output? What do you see instead?
see an error trace like...
08 Mar 2011 14:57:29,976 [http-8080-1] DEBUG (NativeBroker.java
[getOrCreateCollection]:630) - Creating collection '/db/system/temp'...
08 Mar 2011 14:57:29,982 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 5:
/db/system/temp/33873e8b72e9d1240fd6ec9a4231e671.xml
08 Mar 2011 14:57:29,989 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 6:
/db/system/temp/e614cd8668b1bd5ca11ee35a622e2d6a.xml
08 Mar 2011 14:57:29,995 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 7:
/db/system/temp/5b2c1f548c8ec9c35531402073844b7e.xml
08 Mar 2011 14:57:30,001 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 4:
/db/system/temp/033b9f4f3bfbd948a1c724ba25b08a70.xml
08 Mar 2011 14:57:30,007 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 9:
/db/system/temp/05267d4511791a78c0f1ae799668c4bf.xml
08 Mar 2011 14:57:30,012 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 10:
/db/system/temp/3466edc97c4291960c006a5c3236b7b4.xml
08 Mar 2011 14:57:30,018 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 13:
/db/system/temp/2afa4c2bcea546ef2a7d6a280476b544.xml
08 Mar 2011 14:57:30,024 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 11:
/db/system/temp/5c7da32b2c6cec1a590ddb87562b178d.xml
08 Mar 2011 14:57:30,030 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 12:
/db/system/temp/1de06e1baa7ec59bcd30e09d03fc6c10.xml
08 Mar 2011 14:57:30,035 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 14:
/db/system/temp/a4c350ed00beb9f0b77d1d1897f44d31.xml
08 Mar 2011 14:57:30,041 [http-8080-1] DEBUG (XQueryContext.java
[storeTemporaryDoc]:2495) - Stored: 15:
/db/system/temp/f723731dda9fd0320b5cd9c5246f28e2.xml
08 Mar 2011 14:57:30,056 [http-8080-1] DEBUG (XQueryServlet.java [process]:430)
- The actual cardinality for parameter 1 does not match the cardinality
declared in the function's signature: substring-after($source as xs:string?,
$search as xs:string?) xs:string?. Expected cardinality: zero or one, got 11.
In call to function:
atomdb:deprecated-edit-path-info(element()) [128:13]
local:test5() [365:18]
org.xmldb.api.base.XMLDBException: The actual cardinality for parameter 1 does
not match the cardinality declared in the function's signature:
substring-after($source as xs:string?, $search as xs:string?) xs:string?.
Expected cardinality: zero or one, got 11.
In call to function:
atomdb:deprecated-edit-path-info(element()) [128:13]
local:test5() [365:18]
at org.exist.xmldb.LocalXPathQueryService.execute(LocalXPathQueryService.java:192)
at org.exist.http.servlets.XQueryServlet.process(XQueryServlet.java:414)
at org.exist.http.servlets.XQueryServlet.doGet(XQueryServlet.java:171)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
Original issue reported on code.google.com by alimanfoo@googlemail.com on 8 Mar 2011 at 3:00
GoogleCodeExporter commented
This should be fixed in revision 641, but it is hard to test across all
situations, so will re-open if further problems occur.
Original comment by alimanfoo@googlemail.com on 8 Mar 2011 at 3:28
- Changed state: Fixed