AI News Feed
Market watch
TechRadar Shares Friday, October 9 Answers for Quordle, Connections and StrandsElastic Launches AlertZero AI Agents to Tackle Security Alert OverloadiVerify Finds P7 DarkSword Spyware Variant Targeting Unpatched iPhonesFirmus scraps ASX float that would have been Australia's biggest since TelstraBloomberg’s The Close Flags AI Trade, Oil and Treasury Yield Pressures on MarketsDeveloper Ports Doom to Run Entirely Inside a SQL Database
TechRadar Shares Friday, October 9 Answers for Quordle, Connections and StrandsElastic Launches AlertZero AI Agents to Tackle Security Alert OverloadiVerify Finds P7 DarkSword Spyware Variant Targeting Unpatched iPhonesFirmus scraps ASX float that would have been Australia's biggest since TelstraBloomberg’s The Close Flags AI Trade, Oil and Treasury Yield Pressures on MarketsDeveloper Ports Doom to Run Entirely Inside a SQL Database
Products & Applications

Developer Ports Doom to Run Entirely Inside a SQL Database

Lukas Vogel has ported Doom to run inside a SQL database, rendering 640×480 color frames with about 1,300 lines of SQL.

AI News Feed · 2026-10-09 08:38

The port produces 35 full-color frames per second at 640×480 resolution, using roughly 1,300 lines of SQL code divided across 89 query blocks, TechRadar reported. An earlier effort called DoomQL was launched last year and relied on raycasting with grayscale text characters, so it resembled Wolfenstein 3D more than Doom. That raycasting skipped the BSP-tree traversal that helped distinguish Doom's rendering approach, prompting Vogel to develop a second version.

For SQLDoom, Vogel required both the rendering system and game loop to operate entirely through SQL, with output limited to exact-color tables or bitmaps. “Rendering Doom in a database is obviously a bad idea,” Vogel said in a blog post about the project, according to TechRadar.

Building the new version meant recreating key parts of Doom's rendering process using database operations rather than conventional game-engine code. Handling the level geometry was relatively straightforward because a sort key calculated when each map loads lets a single ordering clause determine which wall sections are drawn.

Floors and ceilings presented a tougher problem. Doom's original engine uses visplanes and state changes, neither of which translates neatly to column-by-column SQL rendering. Vogel replaced that system with what he called a “pretty hacky” approach, looping through a sequence of sorted panels to fill those surfaces.

Vogel reports about 60 fps on a laptop with a Ryzen 7 7840U chip, though busy scenes can fall to 35 fps. He said table overhead was substantial, yet the port still ran faster than his simpler DoomQL effort from last year. “I intended it as a tech demo, but it just feels like the real Doom, even though it doesn't share a single line of code with any existing Doom port,” Vogel said.

The port also supports deathmatch play, with public online servers hosted in Europe and the United States open for multiplayer matches. Reviewers who tried the online demos described sluggish performance, with one outlet suggesting the servers rather than the port itself were responsible. Vogel argues a database keeps one steady record of game state, with “no partially applied updates, physics bugs, or disagreements over whether the rocket actually hit.”

The Register noted the work doubles as a showcase for CedarDB, a database system that compiles complex queries into machine code. Anyone wanting to try it can run the GitHub code locally with CedarDB and Doom's original WAD data, or join a free hosted match online.