That is normal behavior. When you run doctrine:build-schema, it puts the entire definition for all of the tables into the config/doctrine/ schema.yml file. The plugin schema.yml file will not be touched, but as you noted the syntax will be slightly different, but should achieve the same results. For this reason, I find it more convenient to make the changes in the config/doctrine/schema file and then run symfony:doctrine:build-all-reload. Once you have a large project with more than a few schema files, using build-schema will cause all kinds of problems, since changes to the general schema take precedence of those definitions in plugin schema.yml files. I personally would suggest trying to make changes in your schema.yml files, or better yet, use migrations.
HTH Casey Cambra On Oct 19, 8:09 am, HiDDeN <[email protected]> wrote: > When I'm working on a project, I usually make modifications directly > to the database, and then I run the "doctrine:build-schema" and > "doctrine:build-model" tasks. > > Doing this with the sfDoctrineGuardPlugin installed, the "sf_guard" > tables will be replicated from plugin/sfDoctrineGuardPlugin/config/ > doctrine/schema,yml into the general schema.yml, so they are being > duplicated in both places, although the syntax is not exactly the > same. > > Is this normal behavior? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
