[X] I have searched for a similar issue in our bug tracker and didn't find any solutions.
Database
PostgreSQL
What happened?
Even if the options is false, index will be created by Cycle\Schema\Generator\Migrations\GenerateMigrations
Sometimes relation db is used just like a persistence storage, with insert/select by id only operation,
not operational db, so index is unnecessary for these cases.
As a workaround, I deleted these indexes in the same migrations.
Cycle\Schema\Generator\Migrations\GenerateMigrations will not find any differences,
so it look like the bug happen only while generate migrations for new table.
No duplicates 🥲.
Database
PostgreSQL
What happened?
Even if the options is false, index will be created by Cycle\Schema\Generator\Migrations\GenerateMigrations
Sometimes relation db is used just like a persistence storage, with insert/select by id only operation, not operational db, so index is unnecessary for these cases.
As a workaround, I deleted these indexes in the same migrations. Cycle\Schema\Generator\Migrations\GenerateMigrations will not find any differences, so it look like the bug happen only while generate migrations for new table.
Version