I much prefer the "schema first" approach. But then I've always approached a project by first working out the schema (generally, at least) and then moving on to code for doing something useful with it.
On Wed, Dec 5, 2012 at 5:22 PM, pete <[email protected]> wrote: > Doctrine was mentioned sometimes. I also think it would be a great idea to > use this ORM for doing all the crazy DB things. There is no need for a self > implementation because doctrine works very well by now. I like the "code > first" approach in doctrine and i'm really missing this in cakephp to write > the model and generate the database. Doctrine has also options to generate > migration files for differences in database tables and models during the > development process. I mean this features should bbe used in future. > greets pete > > -- > Like Us on FaceBook https://www.facebook.com/CakePHP > Find us on Twitter http://twitter.com/CakePHP > > --- > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > Visit this group at http://groups.google.com/group/cake-php?hl=en. > > -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php?hl=en.
