8000 fixed issue #14592: IS_NULL(@x) isn't recognized as a constant expression by jsteemann · Pull Request #14605 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

fixed issue #14592: IS_NULL(@x) isn't recognized as a constant expression #14605

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

Merged
merged 2 commits into from
Aug 21, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Merge branch '3.7' into bug-fix-3.7/issue-14592
  • Loading branch information
KVS85 authored Aug 21, 2021
commit 0017fbcca660e6e849a5d265d9514bc61858e121
10 changes: 9 additions & 1 deletion CHANGELOG
Original file line number Diff line number Diff line change
@@ -1,7 +1,15 @@
v3.7.15 (XXXX-XX-XX)
--------------------

* Fixed issue #14592: IS_NULL(@x) isn't recognized as a constant expression.
* Fixed issue #14592: IS_NULL(@x) isn't recognized as a constant expression.

* Fix response when isBuilding could not be removed from newly created
collection, when agency precondition fails. This can happen, when own rebootId
increment has triggered plan entry to be removed (BTS-370).


v3.7.14 (2021-08-07)
-------------------

* Fixed various problems in GEO_INTERSECTS: wrong results, not implemented cases
and numerically unstable behaviour. In particular, the case of the
Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.
0