Conversation
Notices
-
On a work-related note, the migrations system in Laravel baffles me. I get the concept (a rudimentary form of version control for the database schema), but it kind of feels like if you're using a system that needs the command line anyway, why not make a system that you actually use on the database like you'd use Git on the filesystem, instead of some convoluted setup where you use the command line to start an update, manually write in all of the functionality necessary not only to apply the update but also to un-apply the update, and then go back to the command line to actually run it? (Plus I made a minor code error while I was figuring it out which completely cherryed the test database so lmao pls use transactions to catch those errors tyvm)
Friday, 23-Oct-15 02:19:51 UTC from web-
@redenchilada Offer to ugrade it to something more manageable when you're bored of your usual work and want to score some credit with the bosses
Friday, 23-Oct-15 02:21:31 UTC from web-
@nerthos The rest of the framework is fine, it's just one part that's really strangely half-assed compared to the rest.
Friday, 23-Oct-15 02:22:13 UTC from web-
@redenchilada Especially since the framework makes it so easy to use pivot tables but the migrations system apparently doesn't have a convenience method to make one without manually writing it all out?
Friday, 23-Oct-15 02:23:44 UTC from web
-
-
-