[Proposal] Implement an 'after' modifier to the mysql schema #73
Conversation
|
Yes please! Have wanted this for ages. Can't stand my tables being in random orders. |
|
👍 |
|
This might work for creation, but I know for a fact that SQLite does not support reordering columns. In fact, to emulate that in sqlite you actually have to add and drop columns, or recreate the table. Part of me wants to say that this is really independent of your migrations. If it bothers you I would suggest doing it manually. |
|
How does it not working with SQLite present a problem? The method would just return $this. |
|
Since this is merely a presentation oriented feature and not a functional one, on databases that do not support it such as sqlite I think its perfectly acceptable to just ignore it. |
|
I don't think this is a good idea to implement right now. Thank you though. |
|
I see this has now been added to the core... Not trying to be annoying but can I ask why you changed your mind? Why is this now a good idea to implement but not earlier? Just for understanding the proposal process a bit more... |
|
@helmut well Taylor didn't say it was a bad idea, he said it wasn't a good idea to implement "right now" which was two months ago. Things have obviously changed. hooray. |
|
No huge reasons. Opinions just change sometimes. :) |
…-endpoints Transaction endpoints
It would be great to be able to specify that you want a column to be added to a table in a specific position. This functionality is sparsely supported across all the database types. I'm pretty sure postgres does not allow you to do this at all.
Should this functionality be added to the core or because it cannot be applied to all database types it should therefore be left out?
I've added the code as an example but if you guys want to go ahead I can create some tests and look into adding similar functionality to some of the other database types (the ones that can handle this functionality of course).