IMHO It would depend on if you would like to have the SQL hidden (secure)
or not. In the PAGE it's easily modifiable. I wouldn't put it in the bean as
the bean is
there as a connectivity and i/o kind of mechanism. If you want security with
ease of
change, I'd put it in the database as stored procedures.
One thing however that negates my comment about beans being cio
(connectivity,input,output)
devices, if you put the SQL in the bean, you would have no flexibility for
schema changes
which happen all the time. if your bean is written correctly as a CIO, it
would could and should
have the reflectivity to allow very generic DB access for any schema that
you can come up with.
I'm sure you've probably made your decision by now ... looking at the date
of your post.
Hope I've helped somewhat.
Bill
-----Original Message-----
From: Brian Burridge [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 07, 1999 9:47 AM
To: [EMAIL PROTECTED]
Subject: JSP & SQL Stores Procedures
I just wanted to get some of your opinions on this. We are having an
internal discussion about whether or not to use stored procedures for
our SQL, or to put the SQL in the bean or JSP page.
Does anyone have any recommendations either way? Suggestions?
Brian N. Burridge
Web Analyst
Cox Target Media
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
