On Sun, 2005-05-01 at 18:53 +0200, Gabriel Birke wrote:
> You could avoid the decision if you use the O/R mapper propel:
> http://propel.phpdb.org/wiki/
I'm using Pear DB (via PG). And then I'm going to port to postgresql.
I've got most of the tools I'm going to use for the project worked out.
Ju
> I'm about to start writing a big web app (mostly in PHP). But
> I'm not sure if I should layout the DB first then write the
> app, or should I just start writing the app and add stuff to
> the DB as I need it. How do you guys go about it?
>
> Thanks,
> Dan.
>
Dan,
The single-greatest thin
By asking "What do I need from the app?"
or
"What questions will the app have to answer?"
or
"What information does the client want?"
and going from there.
Those are all just about the same question. From there you can determine
needed inputs, tables, keys, etc.
Cheers - Miles
At 01:45 PM 5/1/200
I'm about to start writing a big web app (mostly in PHP). But I'm not
sure if I should layout the DB first then write the app, or should I
just start writing the app and add stuff to the DB as I need it. How do
you guys go about it?
Thanks,
Dan.
--
PHP General Mailing List (http://www.php.net/)
4 matches
Mail list logo
