Ah - yes! On Thu, Jul 23, 2009 at 2:23 PM, Jacob Coby <[email protected]> wrote:
> > > On Jul 23, 2009, at 3:15 PM, Jeremy Thomerson wrote: > > > Yeah - but it only initializes a DB if you have fixtures, right? I > > personally use a set of release-numbered sql scripts for the DB so > > that it is easier to manage production releases over time. I don't > > use fixtures. So, I think I could use build-all, right? > > No, you're thinking of build-all-load. > > :build-all-load Generates Propel model and form > classes, SQL, initializes the database, and loads data (propel-build- > all-load) > > from the help for build-all: > > Description: > The propel:build-all task is a shortcut for five other tasks: > > ./symfony propel:build-all > > The task is equivalent to: > > ./symfony propel:build-model > ./symfony propel:build-forms > ./symfony propel:build-filters > ./symfony propel:build-sql > ./symfony propel:insert-sql > > See those tasks' help pages for more information. > > You can pass in --classes-only but that's kind of dangerous and easy > to forget (though it does give you a warning and ask for > confirmation). So I just run build-model, build-forms, build-filters, > build-sql by hand. > > > > > JT > > > > On Thu, Jul 23, 2009 at 2:12 PM, Jacob Coby <[email protected]> > > wrote: > > > > On Jul 23, 2009, at 3:07 PM, Jeremy Thomerson wrote: > > > > > Isn't there a propel:build-all (and I assume a similar task in > > > Doctrine) that accomplishes the same thing? > > > > :build-all Generates Propel model and form > > classes, SQL and initializes the database (propel-build-all) > > > > the "initializes the database" part makes it unfit for use. i very > > rarely want to build a database from scratch. generally only when i > > start working on a project, and even then I usually ask for a dump of > > a working database. > > > > > > > > On Thu, Jul 23, 2009 at 1:50 PM, Jacob Coby <[email protected]> > > > wrote: > > > > > > My take on the two terms: > > > > > > generate: make something I'm allowed/encouraged to edit later. > > > generate:crud, generate:app, generate:project, etc. > > > build: rebuild something that's required to run the app but isn't > > > supposed to be directly edited. > > > > > > the build tasks are really kind of a hybrid since they make both > > > editable and non-editable code. at least with propel. i don't have > > > experience with doctrine. > > > > > > for what it's worth, I'd like to see doctrine:build (and propel) > > > default to building models, sql, and forms and add --no-model, --no- > > > sql, --no-form options. you have to run all three tasks after > > > updating the schema. why make it harder for the normal case? > > > > > > On Jul 23, 2009, at 2:34 PM, Kris Wallsmith wrote: > > > > > > > Hello, > > > > > > > > In an effort to reduce the number of tasks in the ORM plugins I've > > > > come up with a new, flexible "build" task. Its usage in the > > Doctrine > > > > plugin would look something like this: > > > > > > > > php symfony doctrine:build --model --sql --forms > > > > > > > > This would be the same as running these three tasks in symfony > > 1.2: > > > > > > > > php symfony doctrine:build-model > > > > php symfony doctrine:build-sql > > > > php symfony doctrine:build-forms > > > > > > > > My question to the group is a semantic one. Tasks currently use > > the > > > > terms "generate" and "build" interchangeably, without any sort of > > > > reason that I can deduce. Can we just choose one and get rid of > > the > > > > other, or am I missing something? > > > > > > > > Thanks, > > > > Kris > > > > > > > > -- > > > > > > > > Kris Wallsmith | Web Developer > > > > [email protected] > > > > 503.734.5700 > > > > > > > > http://twitter.com/kriswallsmith > > > > > > > > > > > > > > > > > > > -- > > > Jacob Coby > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Jacob Coby > > > > > > > > > > > > > > > > > > > > > > > > > -- > Jacob Coby > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
