Compositional Datalog on Sql: Relational Algebra of the Environment
Posted4 months agoActive4 months ago
philipzucker.comResearchstory
informativepositive
Debate
20/100
DatalogRelational AlgebraDatabase Systems
Key topics
Datalog
Relational Algebra
Database Systems
Discussion Activity
Light discussionFirst comment
3d
Peak period
2
84-90h
Avg / period
1.5
Key moments
- 01Story posted
Aug 27, 2025 at 4:09 PM EDT
4 months ago
Step 01 - 02First comment
Aug 30, 2025 at 11:21 PM EDT
3d after posting
Step 02 - 03Peak activity
2 comments in 84-90h
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 31, 2025 at 9:06 AM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45044525Type: storyLast synced: 11/20/2025, 7:55:16 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Unfortunate you can't add new operators in Python the way you can in Prolog or OCaml to get a readable infix syntax like the one you chose but without the misleading operators like <= for :-. (I've done worse, though...)
My maybe inaccurate understanding of recursive CTEs was that they only allow linear occurrences of the recursively defined relation in the query and do not allow many mutually recursively defined relations. These might be per implementation restrictions. These are pretty harsh restrictions from a datalog perspective. I should explore what Postgres offers more. It's just so easy to try stuff out on sqlite.