Bilge
Bilge
@iChenLei Thanks a lot, this definitely does achieve what I wanted to do, although it seems my original point that you cannot namespace a detached ruleset is still correct.
@broberts-mrmc Migration *organization* should be considered a separate topic from *consolidation*. Please create a separate issue to discuss that.
I believe Doctrine also has a command called _rollup_, although it seems [scarcely documented](https://symfony.com/doc/current/bundles/DoctrineMigrationsBundle/index.html#usage), so I'm not sure if it is exactly the same thing. >[rollup] Roll migrations up by...
Is it documented?
I believe they are not explicitly supported, which means you would need to write raw SQL for view migrations. Since the API for views would be similar to tables, it...
No, just write SQL. SQL wrappers are a complete waste of time.
I understand it would not be preventative, but what I am suggesting is you do not waste time implementing a PHP API for SQL when you can, and should, just...
Disagree. The whole pint of Phinx is a database migrations framework. You can (and should) strip away all the SQL wrapping API and nothing of value would be lost. On...
Wrapping SQL has nothing to do with the migrations objective.
No, I completely gave up using the API methods. All migrations are just `execute()` statements in `up()` and `down()` configurations. Phinx will never support the full feature set of Postgres,...