Brian,
Some DBA's I've worked with actually don't like store procedures. Perhaps
because it is not always evident who is affected should a change be
required. Regardless of religious preference, if you can centralize SQL
that performs a business layer need, then I think you should, but that
obviously needs to be well managed. From my standpoint it is certainly
easier to place all the SQL my apps use under the auspices of my apps.
Usually that's in my code.
It really all depends on your needs.
Dan
> ----------
> From: Brian Burridge[SMTP:[EMAIL PROTECTED]]
> Reply To: Brian Burridge
> Sent: Friday, May 07, 1999 12:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: JSP/Stored Procedures
>
> I'm concerned with development time. Right now I love being able to
> simply do a
> query right in my JSP page. I don't want to have to write a stored
> procedure
> every time I need some data (which is virtually every page). But on the
> other
> hand, I am being advised from our DBAs that they are concerned with SQL
> code
> getting lost, and the difficulty in updating it when it is "everywhere".
>
> Of course, for me, I can simply do a search with my editing tool
> (HomeSite) and
> instantly know all the places I access a certain table, so I'm not sure
> this
> concern is an issue.
>
> Brian N. Burridge
> Internet 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".
