0

We currently have several instances of SF3 websites, and we need to create a new bundle that'll be used by some of these instances. To do so, we decided to go with a reusable bundle as discussed here and it seems that everything is working as expected.

The issue we have is regarding entities; how should we create them in the database and, more importantly, how can we update the model when we update the bundle ?

According to a DoctrineMigration's thread this bundle is not to be used the way we want to and the developers do not plan on adding this feature. Another bundle seems to do the work but I am unsure on whether it's a good idea or not.

Some documentation states that it is possible to add a mapping in the doctrine configuration node (like this and that) but I don't think that'll be enough to manage future changes in entities.

Is there any "official" way of doing so ? Did we choose the wrong path and should consider an alternative ?

NaeiKinDus
  • 730
  • 20
  • 30

1 Answers1

0

I may be out of bounds, but couldn't you define manually the mappings from the shared bundle?

orm:
    auto_mapping: false
    mappings:
        MySharedBundleName:
            type: yml
            dir: %kernel.root_dir%/../src/MySharedBundleName/Resources/config/doctrine
Etienne Noël
  • 5,988
  • 6
  • 48
  • 75
  • Yeah sure, I think that'd be the way to go to register the bundle's mapping, but that won't help if any entity has to be upgraded after a change, will it ? – NaeiKinDus Oct 04 '17 at 07:50