On 4 Jun 2015, at 10:16pm, Darko Volaric <lists at darko.org> wrote:
> Here's an example (with a roughly
> JSON notation):
>
> {
> operation: "insert"
> table: "blah"
> columns: ["a", "b", "c"]
> values: [1.3, 2.0, 3.1]
> on-conflict: "replace"
> }
>
> That is equivalent to an INSERT SQL statement, but why form that SQL
> string, possibly using memory and time, when your system can spit out JSON
> (or whatever) effortlessly?
Why invent a new nonstandard notation for database operations when you have SQL
?
Given your JSON expression above it's easy to write code which turns the JSON
into a SQL command. So just do that (either outside SQLite or by creating a
loadable external function for SQLite) and then you can use SQLite exactly as
it is without having to keep modifying your project every time the developer
releases a bug-fix.
The hard work in creating a fork is not in the initial work but in the
maintenance every time the main project gets updated.
Simon.
