+1 vote


As it is not possible to add an index with the value of an embedded object, how can I prevent the export of the .orm files manually from removing the manually added code to include these indexes?

Thank you

enter image description here

related to an answer for: Index on Embedded
in Feature Request by (130 points)


Skipper always export whole code, it's not possible to keep part of code untouched.

What version of Skipper are you using?

Thanks Luddek

My version of Skipper is

Any idea how I can add this type of index that depends on an embedded object?

We have to investigate it. It is possible that this feature is currently missing.

Can you please send me a sample project to [email protected]?

Ok Ludek, I send you a file below

1 Answer

0 votes

Was this ever solved? I too am having the same issue where I'm able to manually specify an embedded field in an entity index directly via the XML mapping, however, I'm unable to do this via Skipper, so I have to manually make the change after every export.

Further to this, where I actually want to create the index is in in a child entity, where the parent entity contains the embeddable. Either way, even on the parent I'm unable to create this index via Skipper whereas it works in Doctrine ORM XML mappings.

by (730 points)