Hi, With sf1.4 + propel 1.6 : I do nearly all the change directly to the database with all the tools i want to use then i reverse generate the schema.yml. I put all the custom orm behavior in schema.custom.yml so i can always safely use the reverse anytime i want without breaking any behavior.
This work better for me because i m not the only one working on the project, database admin like to handle the database change and they don't care about php or any framework you use that generate their sql. I also dont want to write/track manually all the change that the dba could do. I also believe that the approach "don t look at the database just look at object" is not working on big project where there is more than 1 person working on it ( well maybe i ll change my mind about that after using sf2+doctrine2... ) On Jul 30, 2:29 pm, Gediminas Morkevicius <gediminas.morkevic...@gmail.com> wrote: > First of all if you use ORM you should never look at the tables in database. > You should only deal with objects. Your problem is, that you think in > tables, while you are using ORM. There is no more table relation, there is > object relation. And how do you expect someone could easily migrate tables > into objects?, its a different world, and annotation mapping is closest to > it. Yaml and xml is also about schema if you are thinking in this way and > ORM is not about schema, first of all its about relational objects, and the > second how they are stored somethere > > On Sat, Jul 30, 2011 at 12:09 PM, Giovanni > <giovanni.possem...@gmail.com>wrote: > > > > > > > > > Hi zgoniaiko, > > thanks for the answer. > > I'm agree with you: it's matter of taste, but if in example you should > > have to move from doctrine 1.x to 2.x, you have to rewrite the > > schema.yml from scratch. > > Instead, if you start from the DB-schema, you have to modify only some > > rows on the schema.yml and rebuild the PHP-object (that should be the > > same like in the previous version). > > > The "problem" is that only PHP Objects and DB-schema should > > unchangeable from a older Doctrine version to another (otherwise your > > application will not work), so the up-bottom approach should follow > > this way: > > > PHP-Object -> schema.yml -> DB-schema > > > and the bottom-up approach should follow this way (how it works now): > > > DB-schema -> schema.yml -> PHP-Object > > > On you idea the actually up-bottom approach is not really correct > > because it starts from a thing (the schema.yml file) that isn't > > unchangable but it changes from a Doctrine version to another with the > > following problem that you have to rewrite it. > > > Thank you a lot. > > > Giovanni > > > -- > > 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 symfony-devs@googlegroups.com > > To unsubscribe from this group, send email to > > symfony-devs+unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/symfony-devs?hl=en -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
