I always wonder why SQLite didn't expose a programmatic way for creating a query (as opposed to parsing SQL statements). Given that it was designed to be embedded, it seems to me that it would have made far more sense to provide an API based interface. Then, for example, stored procedures would just be function pointers passed as callbacks.
From the repo: "Meta continues to make periodic ad hoc contributions to this fork and merge corrections back to their private repo. The maintainer thanks Meta for this continued informal cooperation."
I always wonder why SQLite didn't expose a programmatic way for creating a query (as opposed to parsing SQL statements). Given that it was designed to be embedded, it seems to me that it would have made far more sense to provide an API based interface. Then, for example, stored procedures would just be function pointers passed as callbacks.
I'm guessing this is a fork of Facebook's abandoned library? https://github.com/facebookincubator/CG-SQL
From the repo: "Meta continues to make periodic ad hoc contributions to this fork and merge corrections back to their private repo. The maintainer thanks Meta for this continued informal cooperation."
CG-SQL = an attempt to give C what Python has had for a long timeconvenient “scripted” work with the database, but without losing speed.This is cool.
Oracle was already doing this in the 1990's with Pro*C.
https://docs.oracle.com/cd/A97630_01/win.920/a96111/intro.ht...
Sybase and Informix also used to have something similar.
PostgreSQL has this: https://www.postgresql.org/docs/current/ecpg.html
Thanks for the heads up.
Is it safe?