Hi, So right now all the migration commands require a --bundle option (which would indicate it should really be an argument, but I digress). However that option is fundamentally flawed since it doesn't really limit the migration scripts to a single Bundle. Well it sort of does, except for the diff command, which will actually scan all entities regardless of the Bundle it is defined in. I checked the doctrine migration configuration and didn't see anything to limit the entities that are being processed. Nor do I really think it makes sense.
Sure if I am providing a 3rd party Bundle it might make sense to provide migration scripts, that users can then reference, but really for an application you need a single project level migration directory. Imagine for example migrating data from one Bundle to another. This wouldn't work if migrations would be managed separately. Therefore I would propose to remove the Bundle option. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
