Does it show? Feel free to vent on your own feelings. It's always good to have anecdotal sound bites in the inevitable flame war I'll eventually have with some zealot.
Originally Posted by Derokorian
I'm only just beginning to get my head around migrations, so I can't quite imagine the circumstances where the rollback/migrate back-and-forth could be very helpful but I think I know what you mean. I'm picturing benefits a bit like how non-destructive/non-linear editing has helped with audio recording. I think the laravel heart is in the right place, if that makes any sense.
Originally Posted by NogDog
So far, migrations seem possibly great for teams, except for the buggy bits with the tools. It also seems handy if one has to frequently shift one's project from one DBMS to another. For an individual (or pair of guys), it seems like a pointless chore that doubles the amount of work for no good reason. I don't recall ever having any trouble creating a new table with many-to-one relationship using good old-fashioned phpMyAdmin -- although I'm not in the habit of defining foreign key relationships. I do recall having my local copy of a site broken because I lack recent db changes made by someone else. This seems very helpful for that kind of thing.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)