Can somebody with much deeper understanding than mine connect the dots between this “idea of parsing naked SQL queries” and the lower-level Zitron @mnemnion just posted ? I appreciate that Zitron is more “normally”(?) suited to provide a parser for the likes of a sqlite interface lib itself (perhaps a native-zig sqlite replacement, as an alternative to zig sqlite wrappers(?)), but could it be valuable to higher-level use? For instance, if @kristoff’s use case was NOT as “simple” as he proposes, but was a bigger project with nested queries, etc., and he still wanted type mapping, would a zig-native Zitron-created sqlite parser be a resource? (Sorry if I’m way off base in my understanding - I’m more used to comfortable territory like python sqlite3 usage as a magic blackbox.)
EDIT: I should clarify that I am a big raw-SQL fan, and have some distaste for ORMs, so this middle-ground of specified-fields “checking” (“simple ORMish flat-mapping”), but with raw SQL exposed right up at the front-end of the code, is my cup of tea. In case that leaning colors any interpretation of my interest in general use of Zitron.