Re: Application logic and Business logic

From: Alfredo Novoa (alfredo_novoa_at_hotmail.com)
Date: 02/28/05 

Date: Mon, 28 Feb 2005 21:34:09 +0100

On Mon, 28 Feb 2005 14:18:02 -0500, Thomas Gagne
<tgagne@wide-open-west.com> wrote:

>We'll have to agree to disagree on that point. Why should an application know
>that to affect a transaction requiring only five parameters that as many as
>seven tables are updated, two of them optionally?

You are assuming a procedural interface and DBMSs should be accessed
using declarative interfaces.

> All the application need
>know is the name of the procedure and the required parameters.

All the application needs to do is to declare the transaction.

> If it becomes
>necessary to update another table or move a column to another I can do so
>without perturbing the application.

Nothing of this is neccessary with a declarative approach.

>Or imagine an application with embedded SQL that needs to be optimized.

SQL optimization is a task for the DBMS. If your DBMS is not able to
optimize the queries then you have a poor DBMS.

>Having to ship a new program to production for such a minor fix is a blunder.
> Better to be able to update the stored procedure without having to ship new
>code.

But you need to ship code to update an stored procedure.

Regards

Relevant Pages

  • Re: chooses not to generate code at all
    ... >>>DBMS is so that the DBMS engine can execute it when triggered by some ... If there is no trigger, ... Stored procedure is one thing. ... > If the procedure execution is not triggered by DBMS ...
    (comp.object)
  • Re: stored proc code always returns null?
    ... described by "but when i call this from inside another stored procedure ... >now the odd thing about this procedure, if the parameter of @tiercode is ... >declare @lastEffectiveDate as datetime ... >RetroContractCountsTierData.TierCode as TierCode from (retrocontractcounts ...
    (microsoft.public.sqlserver.programming)
  • Re: Shredding XML
    ... to determine which field values should be extracted from an XML doc ... The stored procedure works, but the process of dynamically gathering ... DECLARE keycolumns_cursor CURSOR LOCAL ... DECLARE @xPath varchar ...
    (microsoft.public.sqlserver.xml)
  • Re: ADODB.Command
    ... Try to add SET NOCOUNT ON as a very first statement ... Also declare your parameter as adParamInputOutput. ... > because the stored procedure runs another that appends tracking info, ...
    (microsoft.public.vb.database.ado)
  • RE: What stored procedures call this stored procedure?
    ... this in the wrong way - I have the ID of a stored procedure and I'm looking ... > set nocount on ... > declare @rv int ...
    (microsoft.public.sqlserver.programming)