Well, to me this just sounds like you are suggesting writing the code
outside of the database with no advantage.
If done in the DB or externally it is going to incur the same processing hit
on the database, but at least if it is in the DB it will be a
write-once-use-many solution !

Pete
===
http://www.HowToDoThings.com

> Let the web application establish a session with the app server which
> corresponds with the web user's session. The app server does the query to
> the database server and can then send sections of the result set to the

web

> app, as requested. If the web app goes away the app server times out the
> session and closes the query releasing all cached results. This does not
> cause the database server to do more than is reasonable for a database

server.