Unverified50% confidenceFactExact time
FalkorDB 6.0.2's algo.maxFlow procedure accepts only a single relationship type, and passing multiple types raises an error; the behavior is the same on 4.22.1.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedIn v6, FalkorDB's algorithm API is inconsistent: most procedures accept a configuration map, but algo.pageRank still accepts positional parameters.61% similarUnverifiedFalkorDB 6.0.2 has a bug: when a query contains two MATCH … WHERE … IN $list clauses, it silently returns empty rows unless a WITH is inserted between the two clauses.60% similarUnverifiedFalkorDB is a graph database based on sparse matrices and linear algebra operations, compatible with the openCypher query language, and known for low-latency multi-hop traversal.59% similarUnverifiedPostgreSQL enforces unique constraint validation via B-tree indexes at transaction commit; when multiple transactions concurrently insert the same event_id, only one can commit successfully and the rest receive error code 23505.57% similarUnverifiedUnified diff places deleted lines and added lines in the same column, while side-by-side diff places the old version and the new version in left and right columns, and the two differ in the line numbers, line heights, and scroll offsets corresponding to the same change, so they cannot share the same scroll position.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1065420API
curl https://kongchang.com/api/v1/knowledge/claims/1065420MCP
get_claim(id=1065420)