On 31.12.2009, at 14:54, Daniel Lohse wrote: > Well, you are not expressing yourself properly so I can understand > you. Why do you say 'suffer from this limitation'? You can extend > other plugins' schema but you have to make sure to enable all the > plugins by hand and not use enableAllExcept because then the plugins > are loaded in alphabetical order which is not what you want. The > plugin you want to extend the schema of has to be loaded before the > extending plugin. > > Of course, this all only works beginning with symfony 1.3.
the point that i have been trying (but failing to make) is that I want to handle these customizations inside the global project schema.yml (aka config/doctrine/schema.yml) and not anywhere else. so i think it would actually make more sense if the plugin model configurations would optionally be made available as a merge key alias through some magic. this way i could then simply import and selectively overwrite or extend the plugin schema inside my projects schema.yml. regards, Lukas Kahwe Smith m...@pooteeweet.org -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
