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
{{ message }}
Repository navigation
Querying a document collection does not seem to return non-XML files #18
The behavior you see in eXist was true for eXist 5.2.0 and lower, but with eXist-db/exist#3349, the next release of eXist will match the behavior you see in FusionDB. The change was to ensure fn:collection() function would return proper document-node() nodes (containing XML data, not binary data). As an alternative for your use case, consider xmldb:get-child-resources().
Thanks @joewiz. @grantcv1 The change was made so that FusionDB (and eXist-db) become more compliant with the W3C XQuery specifications. There is some explanation and details in the issue that Joe referenced.
For returning a list of URI as your query above is shown, it is actually more efficient to use xmldb:get-child-resources as suggested by Joe.
I hope that helps? Let us know if you need any more support in this area.
Activity
joewiz commentedon Mar 5, 2021
The behavior you see in eXist was true for eXist 5.2.0 and lower, but with eXist-db/exist#3349, the next release of eXist will match the behavior you see in FusionDB. The change was to ensure
fn:collection()function would return properdocument-node()nodes (containing XML data, not binary data). As an alternative for your use case, considerxmldb:get-child-resources().adamretter commentedon Mar 7, 2021
Thanks @joewiz. @grantcv1 The change was made so that FusionDB (and eXist-db) become more compliant with the W3C XQuery specifications. There is some explanation and details in the issue that Joe referenced.
For returning a list of URI as your query above is shown, it is actually more efficient to use
xmldb:get-child-resourcesas suggested by Joe.I hope that helps? Let us know if you need any more support in this area.