The SQLite R*Tree Module

I have started to play around with building a software rasterizer from scratch, and I am wondering if this might be something that I could potentially leverage to cheat at some of the math problems. The document mentions CAD, but I am not sure if the performance is such that real-time (i.e. 30+fps) queries would be feasible over meaningful datasets.<p>Does anyone have any experience directly using SQL for this sort of thing? I feel like there is something here with being able to define a 3d scene in terms of normalized SQL tables, and then running queries over them in order to produce intermediate&#x2F;final output.

Having used this in production before, it&#x27;s an absolutely fantastic tool for specific use cases. My use case was indexing fairly static medium cardinality geo data for lookup within a microservice that we hit from our primary monolith. You get fast spatial indexes and essentially zero additional operational overhead.

I love SQLite&#x27;s software model (embeddable library rather than a separate binary), but I often sorely miss the rich data model provided by postgres. I miss things like strong type checking, special types to represent times&#x2F;coordinates&#x2F;etc., and advanced index types like GiST indices.

Note that even though it&#x27;s a module lot of distributions of Sqlite come with it enabled. You can check it by running<p>PRAGMA compile_options;<p>and looking for ENABLE_RTREE

Mmmmh does spatialite use it? I guess yes. Spatialite is great even though the queries are a little tedious.