Mark Story

After attempting to fix this with #731, I don't think there is a reasonable solution for this deprecation warning. Phinx providers the `getQueryBuilder()` method. All of phinx's branches have moved...

> Is there any documentation about getDecoratedConnection() available? No, but it will return a `Cake\Database\Connection` with the connection that migrations are being run on. That method will be available in...

> That will (in essence) means we have to implement a simple version of phinx in migrations. Yes, we'd need to port & adapt all of the logic required to...

> What are thoughts about using some other Migrations library (e.g. https://www.doctrine-project.org/projects/migrations.html ?) and wrapper any Cake specific things? Does that just end up back at the same place it...

Thank you for the sample migrations. These look like operations we already have in CakePHP's database API so you would be able to use those methods to do some of...

4.3.0 has been released now, and includes the new backend functionality. If you have the time please give it a try and let us know how it works for your...

> Since it no longer relies on phinx, we're not limited to phinxlog... Should we have a seedslog? I regularly add new seeds and run them manually, but it would...

Pull request for issue in https://github.com/cakephp/migrations/issues/647#issuecomment-2233828145 fixed in #728

Thanks for the feedback @umer936 I'm happy to hear that the builtin backend was able to preserve compatibility and fix a bug for you.

> Alternatively, we could see if hasAutoIdIncompatiblePrimaryKey() could be applied per table, instead of per file. Isn't this the better option for end users? Instead of having to learn more...