SQLite documentation is a gem. If you want to write a SQL parser you should definitely see their railroad diagrams (don't ask me why I know this).

Fun fact, jq - the json processor also uses bytecode and some kind of virtual machine to execute queries

sqlite is one of a tiny list of genuinely good pieces of software. probably #1. almost guaranteed to be the most used piece of software ever in the history of forever. everything else pales in comparison, quality, testing, reliability, documentation, usage, portability. truly the mvp of all time. most valuable program.

I’m in the middle of the academic research into bytecode vs ast compilation/execution and this is right up in my valley. Sweet

The reason why SQLite is quite close for contribution si because they want to make sure it stays in the Public Domain. But since in a lot of countries you can't just put something into PD (except by dying and then waiting for Copyright to run out) and in others it's a lot of bureaucratic mess, they decided it's easier to just restrict who can contribute.

Is he pronouncing SQL like “Squeal“ on purpose?

You should read on how they do testing (Richard Hipp also done some talks on it), that's some next level stuff.

SQLite devs: yeah so prepared statements are really just another table in your db

Weird timing to see this video, since I just discovered that it used byte code myself while reading some of the SQLite documentation last week. Hope to see Prime do a video on DuckDB sometime, since it's in-process like SQLite but made for big data and insanely impressive both in features and performance. I've evaluated many databases over the years, and DuckDB is the first one ever that checks every box I have. Was cool to see the creator of SpacetimeDB shout out DuckDB during his presentation on this channel.

I would heavily challenge the statement that no tree-of-objects database provides the level of detail as sqlite. MS SQL and Oracle both have amazingly powerful query inspection tools. In many places it doesn't just explain what it would do or has done but why it chose that physical implementation over another based on stored statistics of the tables and indices. They also allow you to override those choices in the case where you know something the database engine doesn't.

Good video. I remember reading about SQLite dungeon code in college during a compiler class. We had to make a SQL parser. We also had to do a matlab like parser and other stuff. I remember, that I did it in perl. It was like 60 lines of perl (?(DEFINE))xi . I was sophomore and I remember everybody else in the class was a senior. Today I guess most people use ANTLR or LLVM. This was a good clip (refresher).

I think I'm going to have learn more about this it sounds a lot more interesting than I would have expected

Emulator devs that write in Rust may already know, but enums in Rust can be both an AST and a bytecode since the discriminator can have a repr of u8. My implementation does use "unsafe" code to move and dereference the Program Counter pointer, but enums are actually enums in Rust (a way to represent a finite number of states). You had said something about not liking Rust enums, but Haxe and OCAML have pretty much the same thing. They are very useful for making AST representations.

Lol, falling in love with SQLite when I first started using it over 20 years ago. I used it when writing my own client server database system. The server ran SQLite and managed multiple clients by making sure the accesses where put into a queue to run one at a time thereby not trying to do concurrent access on the database. It was for a point of sale system, so custom-ish hardware and at most about 10 clients all on a local network. The real advantage of it was that both the client and server where single exe files, with no complex installation process required. Ever since then I've stored local config in SQLite databases, and just about every application I've ever written consist of only a single exe file. Installation and usage instructions - run the file from wherever you want to. Uninstall instructions - delete the exe file, if you can be bothered.

Most RDB (relational database) that do optimisation will transform the SQL statement into a formal mathematical representation that can be manipulated for optimisation before execution.

11:24 Rusts sql library sqlx actually connects to it's database at compile time and generates those prepared statements already then. That way prepared statements can be used all the time. Edit: Turns out I was wrong and misremembered that part of the documentation. Though having compile-time validation of your queries and per connection caching of your prepared statements is still really cool!

Not sure, but I guess one of the reason that other dbs don't use this approach is that each engine can optimize a query in a different manner, so it's more appealing to rely on a implementation agnostic AST.

man with 20 years experience just learned about sql, nice

THX! dude, i really enjoyed every mitine of the video

The first time I used a DB was in college and it was SQLite. I was too naïve to appreciate its beauty. Their documentation is *chef's kiss*

Database creation is a really interesting thing, you are right

Clang uses byte code (IR) inside LLVM. I would be quite surprised if GCC doesn’t use a byte code internally in the process of compiling. Byte code doesn’t need to be interpreted by a computer simulator to be useful (VM). Byte code isn’t slow or fast on it’s own, like always, it depends.

Randal, a viking i am, i aint no Knight but on quest we go.....

You calling SQL as "squeal" made me smile. Not gonna lie. I've always heard it referred to as "sequel". Nice.

He is the only one who says squeal. Everyone else is saying sequel (sick-well) or ess-que-ell

SQUEAL

You might be pronouncing squirrel wrong

From now on, SQL is squeal to me

Wait, PostgreSQL doesn't use byte code? I just had assumed that of course any SQL engine would use byte code, because it is very easy to do and has quite the performance benefits (especially when using the GCC/clang "address from label" extension with which you can improve byte code interpreter performance).

SQLite's the first (and currently, only) DBMS that I've used while on my development journey and I love how straightforward and simple everything feels, I don't really know enough to know what areas it sucks with, but I've enjoyed using it so far.

19 mins of Prime squealing into my ears

While bytecode (or even machine language) is faster than interpreted code, the resulting implementation of bytecode may actually be slower than interpreted code. It is all about the underlying algorithm used for retrieving the data. A well written algorithm in an interpreted language that also has language commands which are optimized for data retrieval and manipulation will greatly outperform an inefficient algorithm written in bytecode.

Do you have a guide on your TV? Yes, its probably a Sqlite database. Updates of the guide is just downloading the database file😊

One thing I don't like is the terse error messages for constraint violations. I mostly use SQLite for automated tests, so clearer error messages would be very valuable.

writing the three looks so much easier than doing on SQL :,c

And Python includes it in the standard library.

The text to speech engine in this video could use some improvements 🙈

makes sense that it's interpreted for different platforms?

I often used an in memory SQLite DB for testing. Much faster!

Whatching on 0.75x speed 😂

Drive by community contributions is technical debt for everyone else.

So this îs like compiled stored procedures in mssql?

AST integrated into VS Code btw fyi

"Squeal", LMAO

Tree sitter is not very different. It should basically preserve all informations squealitté need to work

If I ever invent an alternative to "SQL", Imma call it "SQUEAL".

I tried to make sqlite work with 200k data and well, my sqlite database died.

See-qual.

SQLite is open source, but closed contribution. This is a very important distinction because things like Redis and Grayjay *_reaaaallly_* want to be able to twist the narrative and FOSS-wash themselves by using terms like "source available" and convincing people it's basically the same or even better than open source. What defines open source is purely and simply "can I use this how I want without your permission?". You can get into some iffy territory when it comes to "free"/Libre distinctions where you reach the question of the right to concede your rights ("Should I, as the user, have the right to concede my right to fork, look at the source code, etc. by using a less-permissively licensed version of the software?") but contribution is entirely irrelevant to that question. Another reason why this is important (aside from shitty people/companies who try to FOSS-wash themselves and weasle into stealing some good PR via deception) is that a lot of people *_think_* open source requires you accept contributions and such, and so use that as an argument to *_not_* open source. Literally all it takes to open source something is to make the repository public and ctrl-c ctrl-v a license into it. Accepting contributions is *_entirely_* irrelevant to it being open source or not. (you'll see a lot of projects that don't quiiiiite FOSS-wash but do try to pretend to be more pro-user than they are hide behind a lot of these sort of arguments) SQLite being open source is precisely why things like like LibSQL can exist; terms like "source available" should be kept exclusively for the shitty projects that try to pretend to be open and pro-user while *_actually_* keeping the user duct taped to the passenger seat, along for the ride wherever the actual driver takes them. (I mean, I'm sure *_some_* projects are pretty honest about it, but I sure as hell haven't seen one)

Can you make a poll to ask where we are from, how we pronounce SQL and how noobs pronounce SQL in their region? How da hell did you pronounce here?

Amazing that none of these small databases don't use EVIs (Encoded Vector Index). Way faster. Come to think of it IBM probably still owns the patents.

Say squeal one more time…

PrimeDB when

Skew-Kuhl is the only correct way to say it

vim is public source and it got slandered for that...

I like how you deal with sponsoring. If you feel you might possibly be biased, you just say so. And even when it's sponsored, I've never felt that you've distorted your point.

I dont really get the point of so much comparison with engines like mysql or postgress. Even though I am not well versed in the database engine development I can imagine that having concurrence is a thing that would make some of the approach to things not possible. Sure sqlite is fast compared with postgress or mysql. but also cat > mydb.txt is faster to mysql, plus as orthogonally similar.

Open-source doesn't necesarilly mean your are allowed to contribute.

Realm DB is even faster than SQLite

It's not squeal-lite, it's "seek-light".

What is squeel?😅

SEQUEL

SQLite was always based. It was always underappreciated

I couldn't watch this the word squeal killed me too much

i cannot get over the fact how you pronounce "sql"

not Squeel its seaquel.

The article screams "developer" and not "DBA". Everyone calls "prepared statements" Execution Plans. A prepared statement is something else. Never heard of a "Tree of Objects". Oracle calls the "objects" in an execution plan Operations. SQL Server calls them Operators. An execution plan is usually, but not always arranged into a tree structure. Things get murky with stored procedures, parallelization, and functions. Don't know about the accuracy of the Bytecode part, but if you're going to analyze a database product's function, do some basic research...

Not sure I can bring myself to listen to someone call it "squeel" for 20 mins

lol, seems like prime never learned relational algebra 😅

Why do you keep calling it squill? is this some sort of rage engagement hack?

I wish Prime would pay a little more attention to what he says is and is not open source. Just because they do not accept changes back into their repo does not mean SQLite is not open source. All that's required of open source is that you are allowed to do whatever you want with your copy of the code

Sho me some fing javescript

Mysqueal and postsqueal... I swear Prime, if I accidentally say this shit aloud on an interview, imma use my particular set of skills and find you... ;)

I think SQL is pronounced “sequel” not “squeel”

I hate it when people misquote things, you have an excuse for it, but there are plenty of other people on the internet misquoting things, and it might not be a huge or significant change, but it's still annoying. I'm referring to 0:00 when he read "SQLite Uses Bytecode" as "SQLite Used Bytecode"

I can't take anyone seriously that doesn't know that it's pronounced sequel

i literally cant listen because of how you pronounce squeel 😭

Come on man, it's "Squeal-ity", not "Squeal-Light"

What the fuck is squeal

I think most of the time public source is shitty. It means there is no real community and you could just have used closed source as well because you have to rely solely on the vendor for everything. You can't even fork it if you think you need to.

It's pronounced "Skull"

SQLite is great and I use it a lot. I'm very thankful to the creators of it, tho I'm a bit disappointed that they're fanatics 😂

I'm sorry, but I just can't get past the pronunciation of words.

Can you remove the scrolling chat from the video? It is distracting

do not worry , coder will be needed for a long time still . Yes even with ai . Your ustensil are smarter

You calling it 'Squeal' is killing me. I could only watch the first 49 seconds of your video before moving on. lol

Structured Query Language (SQL) (pronounced S-Q-L; historically "sequel") is the proper pronunciation. The following quote is from Don Chamberlin who was a researcher at the IBM Almaden Research Center. His employment is notable because it was the birthplace of SQL, and he was a member of the team that developed Structured Query Language (SQL). From a 2001 interview he writes, "We changed the original name "SEQUEL" to SQL because we got a letter from somebody's lawyer that said the name "SEQUEL" belonged to them. We shortened it to SQL, for Structured Query Language, and the product was known as SQL/DS"