Upcoming Laravel 11: SQLite as Default Database

Another interesting change coming to the future Laravel 11 version.

Links mentioned in the video:

- - - - -
Support the channel by checking out my products:

- - - - -
Other places to follow:

[ricko]

I remember facing many weird bugs in one of my laravel projects, after three days of debugging, I realized that I had been using SQLite instead of MySQL, so I switched to MySQL, and all the bugs/errors disappeared completely... all because of some special characters or something like that (im not really sure tbh)

[SXsoft]

Sqlite is ok for projects as long as the developer understands the scope of the project, there is a difference between a presentation website and a CMS/internal tooling panel
You can even use it for some small APIs with caching, but you need to ask the questions from the start, or have your techlead define the starting specs from the start
Had a project in the past where i was using mysql localy and the devops installed MySQL on staging and mariaDB on prod
Since mariadb enforces some things in regards to queries random bugs appeared because of lack of communication

[LoganathanNatarajanlogudotcom]

❤thanks for sharing and i agree the decision

[Marontyne]

Yes, I've always used SQLite for testing. For small projects, I've used it as the main database.

[_plamp_]

I can see this being useful with the introduction of NativePHP

[shubhamsahuSD]

I am a big fan of jetstream scaffolding.

I used to use sqlite on win form, wpf apps and some mobile app for storing small data.

[zulfiqrysaadputra]

I would say this is really good on starting new environment and trying out new things plus easier for beginners on simple projects. So i think this is a good starting point. There are always options for more advanced databases, but i would not really wanna put too much setup phase at the start. Seeing as right now many Laravel tutorials suggest using MySQL for simple tutorial, but obviously you don't need to.

[petkat]

Same as many... SQLite has issues with date types or relations if not set up properly. And I don't want to use totally different database for testing and for production. But I fully understand to this change.

[njhuige]

Interesting! To be honest, I really like to use sqlite for prototypes. You can change the database to mysql later with little effort.

[wowdesigns]

idea .. 👌 what is we do this composer create-project laravel/laravel appname --db=mysql

🤐

[valentin]

what about intervention/imagecache, it's abandoned now, how we can use filters for images and cache them now?

[eslammostafa]

For me I don't use SQLite even for testing purposes, so of course I will switch to MySQL

[scotneymamai]

If you find the time, please do a video of setting up laravel on Oracle 19c or Oracle 21c. O tried deploying a laravel app with Oracle and issues started immediately I started running migrations. The video would help 💯

[coolcha]

Great video again. You mentioned that you changed from SQLite to prod DB technology for your tests as there were some bugs due to the discrepancy - could you highlight / provide some examples of these?

[mikenowak]

Interestingly, Laravel Pulse requires MySQL so a beginner who wants that is going to run into a problem if they try to use that.

[MarkSnape]

I've always been out off sqlite because of lack of decent tooling. What are the options? Only tablePlus?

[porrapatcpe]

I am really agree with this. It likes getting the pros from Ruby on Rails.

[enweremudochukwu]

Laravel 11 requires sqlite 3.35+ while most Ubuntu Distros are still supporting sqlite 3.31 as latest version. I've been developing with Laravel since 2015 and using mysql, but onboarding into sqlite has been faced with more bugs than I can imagine. I wonder how a new Laravel developer will cope.

[fetova]

Honestly, I don't mind using sqlite but, I haven't used it a lot to have issues with it

[albinopepegas]

Why postgreSQL is not used that much? 😂