#aaronpkwell at least they do a good job of documenting the changes
#aaronpkoof yeah i should set aside some time for this. looks like it's going to be hard to have to jump two versions, so gotta get this one out of the way now
#dansup"Laravel makes interacting with databases extremely simple across a variety of database backends using either raw SQL, the fluent query builder, and the Eloquent ORM. "
#dansupdifferent backends? Why would you have multiple databases? Why not one db and one cache
#ZegnatI have yet to see a framework that handles multiple db connections smoothly without the user having to beat the framework with a bat. They are all build on the assumption of 1 storage method and then be done.
#cweiskeplease go back playing in the children's room
#dansupcweiske, you should be using mongodb if you want webscale
#Zegnatdansup, work example? For data segregation clients demand separate databases for their confidential data. But if you don’t want core application data to be duplicated amongst all those databases you will have at least 2 connections at all times: 1 to your application db, 1 to your client db.
#dansupZegnat, oh I see, yeah I have never had to separate data like that
#ZegnatThey are definitely edge-cases, but also not unheard of. They are just not the type of applications people have in mind when building a PHP framework.
#petermolnarI nearly jumped on Laravel, then I had to learn Perl and Python for work. I think destiny made good calls here :)
#petermolnarjoke apart, multiple db connections in PHP is already a problem
#cweiskewe're using multiple databases to keep canonical data in a relational database (mariadb) that's managed via the backend API only, and have a crate.io store for the frontend - which contains enriched data sets optimized for frontend use cases, so that web pages only have to do a few queries instead of multiple complicated ones
#cweiskeeverytime canonical data change, enriched data sets are written into crate
#cweiskeanother case we have is integration testing. spinning up a dozen services on our CI setup is not what I want, so I prefer not to start a full MariaDB/MySQL daemon on each test run. simply exchanging the database adapter with an SQLite one is much easier