| Subject | Re: [firebird-support] Stored procedures vs Dynamic SQl |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-07-13T14:40:56Z |
At 07:40 PM 13/07/2005 +0530, you wrote:
apple pie. They are different eating experiences. If you have an operation
that is achieved by a simple insert, update or delete statement, it doesn't
make sense to push that work into a stored procedure. If you have a
complex operation that imvolves updating multiple tables or (in the case of
selects) needs a set that couldn't be got easily with a single DSQL
statement, then you want a stored procedure.
If you only want to eat the apple, don't make the pastry and bake the pie.
./heLen
>Hi,Yes, like there's a huge difference between peeling an apple and making an
>
>I would like to know if there is a huge difference between using SP or
>Dynamic SQL.I am in process of deciding an architecture where clients
>will be .net smart client,and firebird1.5..I have about 120-130
>tables..Clients,will be of POS terminal type..connected to a central
>server..
apple pie. They are different eating experiences. If you have an operation
that is achieved by a simple insert, update or delete statement, it doesn't
make sense to push that work into a stored procedure. If you have a
complex operation that imvolves updating multiple tables or (in the case of
selects) needs a set that couldn't be got easily with a single DSQL
statement, then you want a stored procedure.
If you only want to eat the apple, don't make the pastry and bake the pie.
./heLen