Bundle-specific Migrations: do I have to create migrations manually?

Hi there,

reading the documentation ‘How to Use Entities’:
https://oroinc.com/b2b-ecommerce/doc/current/dev-guide/entities/using-entities

I failed in finding some command to create a migration scheme for predefined entities automatically.

In Symfony 4 / doctrine one can use simply ( – however, not bundle-specific):
command (corresponding oro-command)

1. $ ./bin/console make:entity (?)
2. $ ./bin/console make:migration (?)
3. $ ./bin/console doctrine:migrations:migrate (.bin/console oro:migration:load –force)

In Oro, how I can create migration scheme automatically?

Thanks for help
Frank

Topic

[Andrey YatsenkoModerator]

OroPlatform uses a bit different migration architecture that plain Symfony.
1,2 commands are not available.

To generate the code for migrations you can use bin/console oro:migration:dump [BundleName], but the command outputs the code to the screen, you should split it to files and save manually.
It is recommended to specify [BundleName] as an argument, otherwise, it will output the migrations for all the bundles that usually not useful.

[FrankParticipant]

Hi Andrey,

correct command seems to be, right?
bin/console oro:migration:dump –bundle [BundleName]

My Entitiy-Classes are:
Acme\Bundle\DemoWorkflowBundle\Entity\PhoneCall.php
Acme\Bundle\DemoWorkflowBundle\Entity\PhoneConversation.php

My Bundle-ClassName itself is:
Acme\Bundle\DemoWorkflowBundle\AcmeDemoworkflowBundle.php

Trying to put some Bundle-Name into the commandline:

PHP

bin/console oro:migration:dump --bundle [AcmeDemoworkflowBundle]

1	bin/console oro:migration:dump --bundle [AcmeDemoworkflowBundle]

or

PHP

bin/console oro:migration:dump --bundle [Acme\Bundle\DemoWorkflowBundle\AcmeDemoworkflowBundle]

1	bin/console oro:migration:dump --bundle [Acme\Bundle\DemoWorkflowBundle\AcmeDemoworkflowBundle]

generates the error:

‘AcmeDemoworkflowBundle is not aknown bundle’

What I am doing still wrong?

Thanks
Frank

[Andrey YatsenkoModerator]

Square brackets were for a placeholder. Correct syntax is:

Shell

bin/console oro:migration:dump --bundle AcmeDemoworkflowBundle

1	bin/console oro:migration:dump --bundle AcmeDemoworkflowBundle

[FrankParticipant]

I’ve got it!

PHP

./bin/console oro:migration:dump --bundle="AcmeDemoWorkflowBundle"

1	./bin/console oro:migration:dump --bundle="AcmeDemoWorkflowBundle"

works fine for me.

Thank you/regards
Frank

[FrankParticipant]

PHP

bin/console oro:migration:dump --bundle AcmeDemoworkflowBundle

1	bin/console oro:migration:dump --bundle AcmeDemoworkflowBundle

works too!

Thank you.
Frank

[FrankParticipant]

Hi there,

I have to revoke my statement!

$ bin/console oro:migration:dump –bundle=AcmeWorkflowBundle

Generates installer-code with existing database tables only.
It is NOT USEFUL, if one have entity-php-classes created and looks for automatic migration-code-generation!!!

oro:migration:dump works only after bin/console doctrine:schema:update has been executed:
https://oroinc.com/b2b-ecommerce/doc/current/dev-guide/extend-and-customize/installer-generate

So, finally it seems, you have to generate migrations-code manually, what is not very comfortable, really!!

Frank

[Andrey YatsenkoModerator]

1) Do a database backup
2) Run doctrine:schema:update
3) Run oro:migration:dump
4) Restore from a database backup
As a result, you have auto-generated migrations for all the entity changes.

[FrankParticipant]

Hi Andrey,

hm. Suggested workaround a ‘little bit’ cumbersome, as mentioned above. However it works.

Would be very comfortable to implement into oro platform something like (available in Symfony 4):
$ ./bin/console make:migration

Thanks a lot.

Kind regrads
Frank

(Topic closed finally)

[Author]

Replies