111–120 of 131 posts
Earlier quoted context omitted.
The initial release of sqlite was in 2000. Yes, well after GNU-style command line options existed but not by much.
22 years is a long time to deprecate bad command line arguments.
Shame. Even bigger shame is that nobody else is taking the torch.
I'm looking through this guys website for 'today I learned' and at first I'm impressed by how many of them there are. But then I start thinking: when you're trying to solve a problem you search for a lot of data. None of his posts are attributed. He's getting all his information from somewhere and then he goes and posts these articles just ripping off other sources. I can understand when its based on your original wo…
This is the author's notebook, which happens to be public. It's okay.
Earlier quoted context omitted.
22 years is a long time to deprecate bad command line arguments.
Sqlite team idolizes backwards compatibility. Which is admirable but at the same time it means we are not getting strong static typing of tables before 2035. Shame. Even bigger shame is that nobody else is taking the torch.
sqlite3 :memory: -cmd '.mode csv' ... It should be a war crime for programs in 2022 to use non-UNIX/non-GNU style command line options. Add it to the Rome Statute's Article 7 list of crimes against humanity. Full blown tribunal at The Hague presided over by the international criminal court. Punishable by having to use Visual Basic 3.0 for all programming for the rest of their life.
sqlite3 :memory: '.mode csv' '.import taxi.csv taxi' \
'SELECT passenger_count, COUNT(*), AVG(total_amount) FROM taxi GROUP BY passenger_count'Earlier quoted context omitted.
22 years is a long time to deprecate bad command line arguments.
Sqlite team idolizes backwards compatibility. Which is admirable but at the same time it means we are not getting strong static typing of tables before 2035. Shame. Even bigger shame is that nobody else is taking the torch.
Earlier quoted context omitted.
Sqlite team idolizes backwards compatibility. Which is admirable but at the same time it means we are not getting strong static typing of tables before 2035. Shame. Even bigger shame is that nobody else is taking the torch.
They added strong typing of tables a few months ago as an opt-in feature, hence keeping things backwards compatible: https://www.sqlite.org/stricttables.html
I had to do something very similar for analysing CVE information recently, but I don't remember having to use the :memory: option. I suspect it defaults to that if no .db file is specified. Slightly tangentially, when doing aggregated queries, SQLite has a very useful group_concat(..., ',') function that will concatenate the expression in the first arg for each row in the group, separated by the separator in the 2nd…
I just tried it without :memory: and it dropped me into the SQLite shell without executing the query: % sqlite3 -cmd '.mode csv' -cmd '.import taxi.csv taxi' \ 'SELECT passenger_count, COUNT(*), AVG(total_amount) FROM taxi GROUP BY passenger_count' SQLite version 3.36.0 2021-06-18 18:58:49 Enter ".help" for usage hints. sqlite>
SQLite's virtual table API ( https://www.sqlite.org/vtab.html ) makes it possible to access other data structures through the query engine. You don't need to know much if anything about how the database engine executes queries, you only need to implement the callbacks it needs to do its job. A few years ago I wrote an extension to let me search through serialized Protobufs which were stored as blobs in a regular data…
I like the virtual table API a lot but it has some serious drawbacks. You don't need to know much and indeed, you can't know much about the execution engine, even if that knowledge would help you. Many parts of the query are not pushed down into the virtual table. For instance, if the user query is: SELECT COUNT(*) FROM my_vtab; ... the query your virtual table will effectively see is: SELECT * FROM my_vtab; SQLite d…
Is it possible to wait until all of the queries are in and then do some query planning at your end to resolve this? Or is it entirely synchronous with no way to do that?
csv mode can also be set with a switch:
sqlite3 :memory: -csv