Re: Big Picture - Mailing list pgsql-novice

From Erik Price
Subject Re: Big Picture
Date
Msg-id DE58317C-E5A3-11D6-A8E5-00039351FE6A@mac.com
Whole thread Raw
In response to Re: Big Picture  (Joel Rodrigues <borgempath@Phreaker.net>)
Responses Re: Big Picture  ("Jules Alberts" <jules.alberts@arbodienst-limburg.nl>)
Re: Big Picture  ("paul butler" <paul@entropia.co.uk>)
Re: Big Picture  ("Josh Berkus" <josh@agliodbs.com>)
Re: Big Picture  ("ken" <kenzo@kennethambrose.com>)
Re: Big Picture  (Giles Lean <giles@nemeton.com.au>)
List pgsql-novice
On Tuesday, October 22, 2002, at 03:08  AM, Joel Rodrigues wrote:

> Or, if one were looking for childishly (in programming terms) easy,
> instant/simultaneous web gratification, try putting as much of your
> application logic into SQL, use Python CGI scripting, and use a web
> browser interface. So simple.

Is "putting as much of your application logic into SQL" the preferred
way to develop DB-driven applications?  I ask this because the only
database I've used is MySQL, which I enjoyed learning about and using
but required me to implement a lot of the DB logic in my application
code.  (It was a PHP app.)  That's why I want to try PostgreSQL, to get
more experience with writing logic into the database itself.  But I was
curious if there are any resources that discuss why this methodology is
preferrable if indeed it is.

Thanks,

Erik

PS:  I agree that Python is a great language!





--
Erik Price                                   (zombies roam)

email: erikprice@mac.com
jabber: erikprice@jabber.org


pgsql-novice by date:

Previous
From: "Jules Alberts"
Date:
Subject: arc relationship [was: db design question]
Next
From: "Jules Alberts"
Date:
Subject: Re: Big Picture