You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every company I've worked with that has used Laravel has kept the timestamps column of a table at the end of the table. That means that when we are adding column migrations (in my current job, we're probably doing this multiple times a week), we have to write for example:
I have to manually go to the database to check which column to place this after, but I often don't care as long as it's 'before the timestamps'. How difficult would it be to get something that worked like this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Every company I've worked with that has used Laravel has kept the timestamps column of a table at the end of the table. That means that when we are adding column migrations (in my current job, we're probably doing this multiple times a week), we have to write for example:
I have to manually go to the database to check which column to place this after, but I often don't care as long as it's 'before the timestamps'. How difficult would it be to get something that worked like this?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions