Hi JohnAD, there is already an issue open : [https://github.com/nim-lang/Nim/issues/9453](https://github.com/nim-lang/Nim/issues/9453)
The sqlite3-part is finished - if you like to dive in please take a look at the sqlite3_examples folder of my project. You can "mix" my module with Nim´s (db_sqlite3). The other modules are (unfinished) on my desk but not forgotten. Discussion and PR´s are welcome. regarding dbNull´s: thats a never ending story - best fit would be "do not handle it within the db-layer". Just let the consumer handle it. It´s a state and not a value - unfortunately handled vendor-specific - always take a look into the vendors's manual regarding dbNulls :-) So if you do a `select null||'hello_nim' from dual` you will be surprised :-) The option-type would be the best fit for Nim I think. But I would not enforce that - if you like to do bulk-processing the option-variant is significant slower than raw-handling. Regarding json on the database I have my own (private) opinion :->
