Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate API to support XQuery 3.1 #4

Open
dizzzz opened this issue Dec 30, 2014 · 2 comments
Open

Migrate API to support XQuery 3.1 #4

dizzzz opened this issue Dec 30, 2014 · 2 comments
Assignees

Comments

@dizzzz
Copy link
Collaborator

dizzzz commented Dec 30, 2014

keywords: Maps, Arrays

@dizzzz dizzzz self-assigned this Jan 10, 2015
@joewiz
Copy link

joewiz commented Dec 29, 2017

+1 ;)

I notice that mongodb:insert supports maps for the $documents parameter, but mongodb:find returns strings rather than maps. This is fine, as we can just use parse-json to handle the results, but now that XQuery 3.1 supports maps and arrays and now that eXist has native support for parse-json (allowing us to drop dependencies on xqjson), I think there are still definitely opportunities to migrate the API to support these nice and convenient features of XQuery 3.1.

Similarly, are you considering bringing the module into line with the EXPath "mongo" spec? I see the function signatures already are map-centric, rather than string-centric, e.g., http://expath.org/spec/mongo#fn.insert, http://expath.org/spec/mongo#fn.find.

If so, I'd be happy to help update the tests, docs, etc. here. Let me know if I can be of assistance.

@dizzzz
Copy link
Collaborator Author

dizzzz commented Jan 2, 2018

thnx @joewiz , yes the intention is to make the extension in line with the spec (my name is on it as well). I had a huge backlog, which is almost done. I'll upload a new version soon...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants