Subject | Re: Good DB design: When to use stored procedures? |
---|---|
Author | maximshiryaev |
Post date | 2008-04-21T10:56:45Z |
Hi.
IMHO,
there are two distinct poles in this topic:
One is a DB as an application server. This way you are tied to a
particular DB and so can use whatever it allowes to structure your
application. Ideally all the business logic should be in SPs.
Second is 3-tier model. Here you are BD-indifferent. All your business
logic resides in some application server like EJB or a like. So you
consider your DB as a black box executing SQL, nothing more. It allows
to exchange DB engines without modification of your application (if
you use standard SQL and DB understands it).
The choice of model is yours.
Maxim.
IMHO,
there are two distinct poles in this topic:
One is a DB as an application server. This way you are tied to a
particular DB and so can use whatever it allowes to structure your
application. Ideally all the business logic should be in SPs.
Second is 3-tier model. Here you are BD-indifferent. All your business
logic resides in some application server like EJB or a like. So you
consider your DB as a black box executing SQL, nothing more. It allows
to exchange DB engines without modification of your application (if
you use standard SQL and DB understands it).
The choice of model is yours.
Maxim.
--- In firebird-support@yahoogroups.com, "Zd" <toldy007@...> wrote:
>
> Hi,
>
> I've read in the FB papers that using stored procedures is highly
recommended because it optimizes network traffic and makes query
execution faster.
>