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

Optimize fn:subsequence #1977

Merged
merged 15 commits into from Sep 3, 2018
Merged

Conversation

@adamretter
Copy link
Member

@adamretter adamretter commented Jun 28, 2018

Closes #1971

Details are written up here: https://blog.adamretter.org.uk/fixing-existdb-range-oom/

@adamretter adamretter force-pushed the adamretter:hotfix/subsequence-memory-use branch from bab5831 to 24a7b91 Sep 2, 2018
@adamretter
Copy link
Member Author

@adamretter adamretter commented Sep 2, 2018

@dizzzz @wolfgangmm I think this is now ready to merged (pending review and CI of course!)

@dizzzz
dizzzz approved these changes Sep 3, 2018
Copy link
Member

@dizzzz dizzzz left a comment

Nice piece of work!

@dizzzz
Copy link
Member

@dizzzz dizzzz commented Sep 3, 2018

All tests pass....

@dizzzz dizzzz merged commit ec5b16a into eXist-db:develop Sep 3, 2018
1 of 3 checks passed
1 of 3 checks passed
Codacy/PR Quality Review Not up to standards. This pull request quality could be better.
Details
continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@adamretter adamretter deleted the adamretter:hotfix/subsequence-memory-use branch Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

2 participants