Tommaso BonviciniIn the context of local databases (e.g. sqlite) I think that using SQL to access data is an overengineered practice. I'm actively thinking at a simpler and faster alternative.
jnr in life@MuAlphaOmegaEpsilon as in accessing SQL data, or another implementation?
@NigelGreenway as in having no SQL language at all.
In a client-server architecture the client doesn't know anything about the server hardware and how/where data is stored, therefore SQL is used by the client to abstract away these details and the server will take care of them.
On a local DB instead you have full control, so having this intermediate SQL layer is unnecessary and just adds complexity. Also, with a local DB you know in advance the queries you will run, so there's no need to have a query planner and optimizer at runtime because you can do all of that beforehand.
I'm just talking at a conceptual level right now.
In a client-server architecture the client doesn't know anything about the server hardware and how/where data is stored, therefore SQL is used by the client to abstract away these details and the server will take care of them.
On a local DB instead you have full control, so having this intermediate SQL layer is unnecessary and just adds complexity. Also, with a local DB you know in advance the queries you will run, so there's no need to have a query planner and optimizer at runtime because you can do all of that beforehand.
I'm just talking at a conceptual level right now.