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
- openCypher: CALL { ... } IN TRANSACTIONS inside an explicit transaction commits its batches on their own (ROLLBACK does not undo them, the batches miss the transaction's own writes)
- SQL and openCypher functions answer HTTP 500 for a wrong or null argument (raw NullPointerException in out('E', null), ClassCastException in geo.lineString(1), DateTimeParseException in ts.rate, ...)
- A relationship created while another transaction DETACH DELETEs its target commits as a dangling edge, listed in an unrelated vertex's IN list (edge-append merge onto a reused chunk RID)
- Edge-list head merge (#11498) attaches a relationship to a vertex created after it: when the target is deleted and its RID reused before the commit, the relationship lands on the new vertex and CHECK DATABASE sees nothing
- openCypher: count(c) over (c:Chunk)-[:R]->(r:Record {key: $k}) walks every :Chunk (COUNT CHAIN PATHS push-down starts at the unanchored end; regression from #9595, 26.9.1 seeks the index)
- fix(#11578): an index key of an undeclared property holds the text of an array's content, not its identity
- fix(#11589): wrong or null function arguments that leaked JDK exceptions are refused as illegal arguments or answered null
- The peer-dial census checks the request-start rule in only two named modules, so a dial added in any other module that forgets the cluster credential is invisible to it (sibling of #11452, which #11525 did not touch)
- The DELETE VERTEX modifier is dropped at parse and at render, so a DELETE VERTEX round-trips to a plain DELETE
- GraphQL Long scalar accepts a Float literal (and a Float variable value): a decimal is bound to a Long-typed filter and silently matches nothing
- Docs
- not yet supported