arcadedb
https://github.com/arcadedata/arcadedb
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
not yet supported0 Subscribers
Add a CodeTriage badge to arcadedb
Help out
- Issues
- READ_COMMITTED: a transaction that gave a vertex its first relationship deletes only its own after a concurrent commit added another, and the edge-list head merge commits it
- openCypher: an aggregate inside a map projection, a map literal entry or a reduce() is not treated as an aggregation, so RETURN p{.name, friends: collect(f.name)} answers an empty row
- openCypher: LOAD CSV ... AS row MATCH (n {id: row.id}) matches nothing and writes nothing, because the optimizer runs the MATCH before LOAD CSV binds row
- SQL: since the #11618 fix, an OR that holds a SEARCH_INDEX / SEARCH_FIELDS arm resets to 0 the $score set by a SEARCH_INDEX_MORE / SEARCH_FIELDS_MORE arm, while $similarity keeps its value
- openCypher UNION column check compares RETURN item texts and treats `*` as a literal column: branches with different columns are accepted, branches with the same columns are refused
- openCypher ignores a dynamic $(...) label outside the node scan: WHERE n:$('B') is always true, a hop target (b:$('B')) matches any label, and -[:$('R')]-> matches any type
- An index on an undeclared property keys a list by its toString, so [1.5, 2] and [1.5, 2.0] (equal under =) are two keys: the Cypher seek misses, MERGE duplicates, a UNIQUE constraint admits both
- MongoDB find, count, aggregate, update and delete accept collation, hint, max, returnKey and unknown fields with ok:1 and ignore them, and a delete limit other than 0 or 1 is accepted
- SQL MATCH `<-E->` is a hop in both directions at the top level of a path and an incoming hop inside `.( )`, because the two arrow visitors decide direction differently
- CHECK DATABASE, ALIGN DATABASE and BACKUP DATABASE roll back the caller's open transaction, discarding its earlier writes, and the next statement fails with "Transaction not begun"
- Docs
- not yet supported