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)
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
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.
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.
A little off the subject but still on the subject of sqlite Having a problem with setting up Laravel 11 and its sqlite in a cPanel! Everyone that has a tutorial on how to setup Laravel in a cPanel are also using MySQL not SQLite outside of installing the site in a separate file in the home path and then putting the public file in the public.html file then pointing the index.php file to look in the right paths and adding the .env file is there anything else I need to do to get the site to come up and work? P.S. this is using Godaddy hosting!
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 💯
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.
@@LaravelDaily well , they company I work for likes to do it this way .. they didnt installed the Laravel installer 😁 it'd better to do laravel new demo .. then doing composer create-project laravel/laravel demo .🤷♂
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?
5:20 Disagree. It feels like Taylor did that quietly, and why’s the majority are upvotes on the PR despite his Twitter/X poll showing that we actually prefer MySQL for local dev.
Sqlite has a file where it reads/writes data to, mysql requires a locally hosted webserver with a mysql server on it, e.g. XAMPP. So starting with sqlite doesn't require you to install anything else.
Only EXPERIENCE dev know why a FRAMEWORK need to use sqlite as DEFAULT one, and MUST support big database like Mysql of Oracle, Mysql of Mariadb, Postgre, etc. Larevel makes good choice as a Framework.
Am I the only one who thinks this is... irrelevant? It's very easy to build with SQLite, but for new PHP developers this can't be good because they always start with tools like XAMPP. And for advanced developers, changing databases is a trivial action.
what irritated me the most is not considering the polls' results, why asking in the first place? just change the default to sqlite and we'll switch to mysql back.
How about not having a default, but rather having a requirement. This forces the user to always select a data abstraction. And simply Laravel can suggest SQLite.
SQLite is a bad decision , there is no practical value short of a locally running application with a single user, yeas have in the list of supported engines, but please, not the default. i am still holding my head, why? MySQL may not be the default database for many, bit SQLite is sure to provide a negative experience for a broader swath of developers.
I use Twitter in a non-standard way. I don't follow many people and I don't read the official feed. I read a specific search feed on "laravel" as a keyword.
Strong dislike (for the change, not the video). They're coming in the Google/FB way: we know how you would be better, so we change it by default and you have to perform one (or more) more actions to return everything to how it was before and how you are used to. Bullshit
i dont like the change. i'm of the opinion that laravel should be developed for laravel users, not the people transitioning from other tech stacks. it's equally as easy for them to change the db driver to sqlite in env as it is for us to change it back to mysql
This very bad move, all most of successful laravel projects, are built on MySQL. Why do you want us to start with SqLite? Laravel is killing itself now
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)
This makes me think this change is a bit of a double edged sword. But, that is a lesson worth learning, so maybe it's a good thing overall
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
Yes, I've always used SQLite for testing. For small projects, I've used it as the main database.
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.
I can see this being useful with the introduction of NativePHP
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.
what about intervention/imagecache, it's abandoned now, how we can use filters for images and cache them now?
Sorry I haven't worked with that package and cant help. Maybe spatie have something alternative?
older version of intervention/image still work on laravel 10
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.
A little off the subject but still on the subject of sqlite
Having a problem with setting up Laravel 11 and its sqlite in a cPanel!
Everyone that has a tutorial on how to setup Laravel in a cPanel are also
using MySQL not SQLite outside of installing the site in a separate file in the
home path and then putting the public file in the public.html file then pointing the
index.php file to look in the right paths and adding the .env file is there anything
else I need to do to get the site to come up and work?
P.S. this is using Godaddy hosting!
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 💯
I've never worked with Oracle, sorry
Interestingly, Laravel Pulse requires MySQL so a beginner who wants that is going to run into a problem if they try to use that.
Interesting! To be honest, I really like to use sqlite for prototypes. You can change the database to mysql later with little effort.
"little effort" , if you use full eloquent , probably yes
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.
I've always been out off sqlite because of lack of decent tooling. What are the options? Only tablePlus?
Yo sigo usando HeidiSQL desde hace años pero nose si llamarla decent tooling
❤thanks for sharing and i agree the decision
For me I don't use SQLite even for testing purposes, so of course I will switch to MySQL
idea .. 👌 what is we do this composer create-project laravel/laravel appname --db=mysql
🤐
Yeah, pretty sure Laravel Installer will have that as a choice or a flag, so I advise you use "laravel new" instead of "composer create-project"
@@LaravelDaily well , they company I work for likes to do it this way ..
they didnt installed the Laravel installer 😁
it'd better to do laravel new demo ..
then doing composer create-project laravel/laravel demo .🤷♂
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?
I don't have specific examples, but they were related to using specific SQLite/MySQL functions or syntax differences in raw queries.
@@LaravelDaily so as long as you only use eloquent would you say you wouldn't notice a difference?
I am really agree with this. It likes getting the pros from Ruby on Rails.
5:20 Disagree. It feels like Taylor did that quietly, and why’s the majority are upvotes on the PR despite his Twitter/X poll showing that we actually prefer MySQL for local dev.
Why is sqlite easier than mysql?
Sqlite has a file where it reads/writes data to, mysql requires a locally hosted webserver with a mysql server on it, e.g. XAMPP. So starting with sqlite doesn't require you to install anything else.
Honestly, I don't mind using sqlite but, I haven't used it a lot to have issues with it
Why postgreSQL is not used that much? 😂
I dont know PostgreSQL is great database
Most hostings not provide postgresql right now, maybe one day
Only EXPERIENCE dev know why a FRAMEWORK need to use sqlite as DEFAULT one, and MUST support big database like Mysql of Oracle, Mysql of Mariadb, Postgre, etc. Larevel makes good choice as a Framework.
This is cool
Finally
Am I the only one who thinks this is... irrelevant? It's very easy to build with SQLite, but for new PHP developers this can't be good because they always start with tools like XAMPP. And for advanced developers, changing databases is a trivial action.
Ok!
what irritated me the most is not considering the polls' results, why asking in the first place? just change the default to sqlite and we'll switch to mysql back.
How about not having a default, but rather having a requirement. This forces the user to always select a data abstraction. And simply Laravel can suggest SQLite.
I really like this switch to use sqlite by default.
sqlite is not popular because it's made for development or small projects.
Feels like Laravel is running out of road.
SQLite is a bad decision , there is no practical value short of a locally running application with a single user, yeas have in the list of supported engines, but please, not the default. i am still holding my head, why? MySQL may not be the default database for many, bit SQLite is sure to provide a negative experience for a broader swath of developers.
Am I the only one who noticed you don't follow Laravel? 😅
😁 The company I work for is still using Laravel 8 ..
Missing out The Livewires 3.0 and the newer php features 🤐
I use Twitter in a non-standard way. I don't follow many people and I don't read the official feed. I read a specific search feed on "laravel" as a keyword.
@@LaravelDaily and I think it's beautiful
Strong dislike (for the change, not the video). They're coming in the Google/FB way: we know how you would be better, so we change it by default and you have to perform one (or more) more actions to return everything to how it was before and how you are used to. Bullshit
a poll is not an election :) it could be to find out how many naysayers he need to deal with and be prepared for it
i dont like the change. i'm of the opinion that laravel should be developed for laravel users, not the people transitioning from other tech stacks. it's equally as easy for them to change the db driver to sqlite in env as it is for us to change it back to mysql
This very bad move, all most of successful laravel projects, are built on MySQL. Why do you want us to start with SqLite? Laravel is killing itself now
??? its a config value u know u can just change it