4 ms·
Ugh, CTE's to construct a tree/graph in SQL Server brings back terrible memories. I'd estimate 25% of our time at one point was spent building aggressive cachin
by crescentfresh 12y ago
Ugh, CTE's to construct a tree/graph in SQL Server brings back terrible memories. I'd estimate 25% of our time at one point was spent building aggressive caching in front of it due to the awful performance as more nodes were created.
On a different product now (using PG) and guess what has come up? We need tree nodes! My first thought: anything but CTEs. ltree, materialized paths, neo4j, anything but CTEs. They've just burned me so badly before I'm too afraid to try them in PG.
- jimktrains2 12y agoI worked at a place that had recursive ACLs. We used CTEs and it was pretty darn quick. We only had on the order of a million records, though, so ymmv.
- hobs 12y agoHow quick is quick? (ms?) What kind of hardware were you running? (all data in ram?) Just wondering, still interested in the topic!