![]() ![]() I use database refresh, but in previous versions of the framework that tore down and migrated the database for each test, which was very slow. Even if it is still having to to that same process in the background at least I don't have to keep rewriting that logic and hope I don't mess it up. Part of me wants someone to tell me it's nothing significant and give me permission to switch back to MySQL.Īnd part of me wants someone to show me a tool that can do the work of creating a new table and moving data for me so migrations with custom column ordering is just as simple in Postgres. Part of me truly wants to know what the big deal is and why the DB experts say to use Postgres over MySQL. Or perhaps what would I loose if I decided to migrate to MySQL instead? So the question is what am I gaining by putting up with not being able to change column order. And to do so whithout breaking foreign key constraints. ![]() ![]() Problem is to get that I have to create these crazy migrations that rename a table recreate it with the columns in the order I want them move data to the new table before dropping the old one. Seems simple I know but call me OCD even though it only affects me and only when I'm accessing it in TablePlus I want a logical order to my columns. Why is Postgres better than MySQL?Īfter using Postgres for awhile and having to add to the schema I find myself annoyed by the inability to choose the column order. When I was writing my app I had heard a couple of different DB experts in Laravel related podcasts argue that we should use Postgres over MySQL. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |