| 1. | | We ported the original Doom to SQL (cedardb.com) |
| 339 points by Vaslo 31 days ago | past | 55 comments |
|
| 2. | | We ported the original Doom to SQL (cedardb.com) |
| 6 points by Alephinitesimal 31 days ago | past |
|
| 3. | | We ported the original Doom to SQL (cedardb.com) |
| 2 points by shscs911 32 days ago | past |
|
| 4. | | We ported the original Doom to SQL (cedardb.com) |
| 3 points by kciter 41 days ago | past | 1 comment |
|
| 5. | | We ported the original Doom to SQL (cedardb.com) |
| 9 points by Vaslo 41 days ago | past | 1 comment |
|
| 6. | | Porting Doom's game logic and renderer to SQL (cedardb.com) |
| 6 points by durner 42 days ago | past |
|
| 7. | | Encoding or Compression: Why not both? (cedardb.com) |
| 2 points by eatonphil 3 months ago | past |
|
| 8. | | DoomBench – benchmarking data stacks running Doom (cedardb.com) |
| 3 points by krishadi 4 months ago | past |
|
| 9. | | DoomBench – Can Your Data Stack Run Doom? (cedardb.com) |
| 7 points by SchwKatze 5 months ago | past | 2 comments |
|
| 10. | | Efficient String Compression for Modern Database Systems (cedardb.com) |
| 2 points by tanelpoder 9 months ago | past |
|
| 11. | | Efficient String Compression for Modern Database Systems (cedardb.com) |
| 153 points by jandrewrogers 9 months ago | past | 47 comments |
|
| 12. | | Why German Strings Are Everywhere? (cedardb.com) |
| 69 points by byt3h3ad 10 months ago | past | 55 comments |
|
| 13. | | Stop Nesting Database Systems (cedardb.com) |
| 2 points by pfent 10 months ago | past |
|
| 14. | | Generating tailored and efficient code for every query (cedardb.com) |
| 2 points by teleforce 11 months ago | past |
|
| 15. | | Down with Template (Or Not) (cedardb.com) |
| 3 points by aw1621107 on Nov 2, 2025 | past |
|
| 16. | | Building a DOOM-like multiplayer shooter in pure SQL (cedardb.com) |
| 255 points by lvogel on Sept 9, 2025 | past | 39 comments |
|
| 17. | | The CedarDB Community Edition (cedardb.com) |
| 2 points by dunefox on June 11, 2025 | past |
|
| 18. | | The CedarDB Community Edition (cedardb.com) |
| 12 points by avinassh on May 14, 2025 | past | 1 comment |
|
| 19. | | Fast Compilation or Fast Execution: Just Have Both (cedardb.com) |
| 1 point by mpweiher on April 3, 2025 | past |
|
| 20. | | Tailored Code Generation for Every Database Query (cedardb.com) |
| 1 point by lvogel on April 2, 2025 | past |
|
| 21. | | Optimistic Locking in B-Trees (cedardb.com) |
| 184 points by uds5501 on March 7, 2025 | past | 54 comments |
|
| 22. | | To B or not to B: B-Trees with Optimistic Lock Coupling (cedardb.com) |
| 2 points by lvogel on March 6, 2025 | past |
|
| 23. | | Why Trees Without Branches Grow Faster: The Case for Reducing Branches in Code (cedardb.com) |
| 1 point by PaulHoule on Feb 12, 2025 | past |
|
| 24. | | The Decline and Fall of In-Memory Database Systems (2024) (cedardb.com) |
| 2 points by refset on Feb 6, 2025 | past |
|
| 25. | | Why Trees Without Branches Grow Faster: The Case for Reducing Branches in Code (cedardb.com) |
| 5 points by eatonphil on Jan 29, 2025 | past |
|
| 26. | | Offset Considered Harmful Or: The Surprising Complexity of Pagination in SQL (cedardb.com) |
| 3 points by thunderbong on Dec 27, 2024 | past |
|
| 27. | | The Decline and Fall of In-Memory Database Systems (cedardb.com) |
| 2 points by ChrisWint on Dec 3, 2024 | past |
|
| 28. | | Offset Considered Harmful Or: The Surprising Complexity of Pagination in SQL (cedardb.com) |
| 6 points by pfent on Nov 19, 2024 | past |
|
| 29. | | How to Correctly Sum Up Numbers (cedardb.com) |
| 41 points by sebg on Oct 31, 2024 | past | 44 comments |
|
| 30. | | A Deep Dive into German Strings (cedardb.com) |
| 10 points by tosh on Oct 23, 2024 | past | 6 comments |
|
|
| More |
