Re: But a fool with a tool is still a fool


I never said to put *everything* in stored procedures.

You did say you were going to keep moving your logic into the database. Moving that way is the wrong way, IME.

If you're saying that this typically happened for you, I'm surprised.

Why? If you have only very minor changes, then you're lucky.

Sounds like a pretty bad abstraction, with business logic in multiple areas.
Something I thought you'd be against from the start.

I am. You always need some business logic in the app, therefore also putting it in the database is to be avoided. That is by definition a bad abstraction.

This is true anytime you have more than a single module/executable as
part of your application. You've always got to be sure the modules are
in sync. The same applies to the database schema.

It's true if you have just the one module.

Yet, this seems to be the reason that you replied to my post to debate the
practice of using stored procedures.

You were advocating moving your business logic into stored procs. You said it was because the business logic works directly with the data. Yet putting logic in stored procs is separating it from data. It's the same as using records and standalone procedures/functions.

Using only stored procs is your approach taken as far as it will go. It is a terrible way to develop software. The further away you get from using all stored procs the better for development and maintenance.

Cheers,
Jim Cooper

_____________________________________________

Jim Cooper jcooper@xxxxxxxxxxxxx
Skype : jim.cooper
Tabdee Ltd http://www.tabdee.ltd.uk

TurboSync - Connecting Delphi to your Palm
_____________________________________________
.

Relevant Pages

  • Dynamic SQL in Stored Proc
    ... I have a database setup so that NO users have READ, ... Dynamic SQL and they have stopped working. ... error message when executing one of the stored procs. ...
    (microsoft.public.sqlserver.security)
  • RE: visio 2003 is greedy for memory
    ... I am building a database diagram ... > and each time I am adding a new entity, moving down or up a database ... > I do not have Visual Studio or an old version of Microsoft Visio ... > The new service pack has not fixed that high memory consumption. ...
    (microsoft.public.visio.general)
  • Re: Access 97 to a more powerfull platform!?
    ... Moving to SQL Server is common when a database "outgrows" ... Design problems are far and away the usual reason why a database ...
    (microsoft.public.access.gettingstarted)
  • Re: Confused about proc vs. dynamic SQL vs LINQ
    ... where people create stored procs which *just* call normal CRUD ... for no reasons other than dogma. ... theoretical "change the database and the procs implementation, ... It depends on the database server, but I believe that using a cached ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: File Location Changes & Missing Databases
    ... No, it's not moving, it's being copied, and they're not available in the ... Recycle Bin. ... it probably means that your original song got deleted. ... I thought I'd try the database corruption instructions in KB (article not ...
    (microsoft.public.windowsmedia.player)