SQLite is very similar to Excel/Spreadsheet like apps, a cell can hold any value unless you strictly specified a type, although nobody hates Excel for that as far as I know. The best thing about SQLite is that it doesn't require any installation other than your app. Thanks Aaron
Yes! I need to learn Rust with some motivation that come from Aaron Francis podcast and TH-cam Video PHP doesn't suck (anymore) Why not! Learning Rust is the same as I will become rust that can stick to sturdy scrap metal. That's quote in my DEV blog: You're re-motivated me Aaron! Now Turso/libSQL is near PHP Ecosystem. Thank you!
Love that you struck out on your own but u deserve/need a full-time sponsor so u don't get spread thin doing 1/2 business management and 1/2 content creation, otherwise the stress will bleed into your videos. The world needs a relaxed AF with a dewy glow getting paid $600k/yr to drop deep cuts on us. You changed the game on SQL content, and you're a magnet for whatever tech you demonstrate so long as it's the same tech across across months/years. I hope some bluechip exec is smart enough to realize this.
Curious what the history is for the reason they chose dynamic types by default. Seems like a bit of a gun if you don't know this behavior and expecting the strict mode by default. Might have the dig up the docs to see why
Very helpful distinction - thanks. I've been mulling on a different question (I know, not what this video is about!): possible ramifications of the fact that SQLite is ... dunno if this is the right word ... "limitedly typed": null, integer, real, text, or blob, and (as I understand it) that list will never grow. I'm wrestling with the whole UUID/GUID question, and whether they can be done well and efficiently in SQLite (e.g. using a UUID as the PK, and with/without the "rowed"). Got a bunch of sub-questions / thoughts, including when and how that's a good idea anyway, but interested to know if you'd have something helpful to point me towards.
You can use a column of type "TEXT" as the primary key. However, your application would have to generate the GUID and include it in the insert as SQLite does not currently generate GUIDs (that I'm aware of.) That would be a cool feature if they ever added it.
Would creating a table from Laravel migration set it as flexible as default? or are there anyway to set it as strict from Laravel blueprint migration side?
Haha thanks! But to the important question: these are from Western Rise but I'm on the hunt for a new supplier. They're not as good as the price suggests.
@@aarondfrancis It was funny joke but seriously I found it very similar to JS == and ===, one coerces and one does strict type checking , same concept as far as I understood it :p
this is interesting because what you're seeing in common with SQLite and JS is that they're both weakly typed - as in, data types are implicitly coerced. I'm not sure why the SQLite docs don't like calling the type system weakly typed, it's the correct label for this type of behavior in other programming languages
Prefer to read instead of watching? Check out the article version of this video: aaronfrancis.com/2024/sqlite-is-not-weakly-typed-bfc98b9c
My coding skills are not weak, they are flexible
Aaron please never stop making videos im begging you
😍 I gotchu!
And please keep responding to every single comment
@@vikingthedude haha I'll do my best but no promises there 😂
Man, I love your enthusiasm and openness! Very nice tips going on here!
The passion is the only thing that keeps me glued. The knowledge simply follows from the later.
SQLite is very similar to Excel/Spreadsheet like apps, a cell can hold any value unless you strictly specified a type, although nobody hates Excel for that as far as I know.
The best thing about SQLite is that it doesn't require any installation other than your app.
Thanks Aaron
the pacing on this video is perfect. go quickly in the beginning to get everyone caught up to speed, then explain what's going on
Turso works like a charm. nice video 💪🏻
This is the type of content I'm looking for.
Love your series on MySQL, keep up the good work!
The wink made me chuckle
It was very helpful.
Yes! I need to learn Rust with some motivation that come from Aaron Francis podcast and TH-cam Video PHP doesn't suck (anymore)
Why not!
Learning Rust is the same as I will become rust that can stick to sturdy scrap metal.
That's quote in my DEV blog: You're re-motivated me Aaron! Now Turso/libSQL is near PHP Ecosystem. Thank you!
I'm so so excited to play with all the stuff you've been doing. I just need 8 days in a week 🥵
@@aarondfrancis I've 1 kid, you have 2, maybe you need to doubled it and make it 16 days in a week!
@@panggilmeiam I have four 🤐 2 sets of twins! So I'm well into the doubling already 🥵
@@aarondfrancis OhMyPunk! That's really amazing!!! Btw, I am really thank with you man... you're amazing person!
More SQLite videos please!!! 😊
Love that you struck out on your own but u deserve/need a full-time sponsor so u don't get spread thin doing 1/2 business management and 1/2 content creation, otherwise the stress will bleed into your videos. The world needs a relaxed AF with a dewy glow getting paid $600k/yr to drop deep cuts on us. You changed the game on SQL content, and you're a magnet for whatever tech you demonstrate so long as it's the same tech across across months/years. I hope some bluechip exec is smart enough to realize this.
I also need me to have 600k a year!
Awesome videos and very enjoyable. What color schemes do you use in the editor and terminal?
Curious what the history is for the reason they chose dynamic types by default. Seems like a bit of a gun if you don't know this behavior and expecting the strict mode by default. Might have the dig up the docs to see why
Honestly I think the creator just prefers it. He says as much in the docs
That’s why you always read the documents.
What I've read in the docs basically boiled down to "dynamic types were popular at the time"
Great video! Is there a way to have strict behavior but allow a specific combination of types for example, integer OR string, but not anything else?
This is helpful. Thanks 😃
Very helpful distinction - thanks.
I've been mulling on a different question (I know, not what this video is about!): possible ramifications of the fact that SQLite is ... dunno if this is the right word ... "limitedly typed": null, integer, real, text, or blob, and (as I understand it) that list will never grow. I'm wrestling with the whole UUID/GUID question, and whether they can be done well and efficiently in SQLite (e.g. using a UUID as the PK, and with/without the "rowed"). Got a bunch of sub-questions / thoughts, including when and how that's a good idea anyway, but interested to know if you'd have something helpful to point me towards.
You can use a column of type "TEXT" as the primary key. However, your application would have to generate the GUID and include it in the insert as SQLite does not currently generate GUIDs (that I'm aware of.) That would be a cool feature if they ever added it.
Very informative 🎉 thank you!
Great video, great info!! 👍👍👍👍
will you ever review sqlpremium
I... don't know what that is
@@aarondfrancis lite is the free version right? so kinda assumed there would be a paid premium version
😂 that went way over my head
@@Pbertrand_dev lol, there is not. Although I suppose Turso is a premium version!
@@Pbertrand_dev 🤣 This one got me cracking.
Would creating a table from Laravel migration set it as flexible as default? or are there anyway to set it as strict from Laravel blueprint migration side?
Cool. Nice video.
where do you get your black t's at?
Oh! Great video btw, as always
Haha thanks! But to the important question: these are from Western Rise but I'm on the hunt for a new supplier. They're not as good as the price suggests.
Is that sqlite video or 😂😂😂😂
Huh?
SQLite == JS
How dare you!
Man, that was some gratuitous offense
@@aarondfrancis It was funny joke but seriously I found it very similar to JS == and ===, one coerces and one does strict type checking , same concept as far as I understood it :p
@@RaflusEK haha you're totally right, I was just bein silly
this is interesting because what you're seeing in common with SQLite and JS is that they're both weakly typed - as in, data types are implicitly coerced. I'm not sure why the SQLite docs don't like calling the type system weakly typed, it's the correct label for this type of behavior in other programming languages
Handsome gay WASP
Not gay, but thank you!
First 🎉 😅