[MUD-Dev] Re: The total DBMS approach

[Sean Kelly]

On Thu, 15 Aug 2002 Daniel.Harman at barclayscapital.com wrote:
> From: Hanz, Rob
 
>> As of version 4.0, MySQL can use row-level locking, if you use
>> the InnoDB handler.  It also has support for transactions,
>> meaning the only major functionality missing is stored procedures
>> and nested select statements.
 
> Hmm, how do you make a properly n-tier app without sprocs? Do
> people using MsSQL really have to embed the SQL in their code as
> that doesn't sound maintainable or easy to optimise (as you can't
> let a DBA optimise your queries independantly of you).

> Furthermore, I was under the impression that using sprocs allowed
> the RDBMS to optimise queries more effectively than SQL squirted
> directly down to it.

Stored procedures are precompiled, and often cached, so execution is
typically far faster than ad-hoc queries.  Also, as you say, there's
the abstraction issue.  For queries, views offer some of the
benifits of stored procs (pre-calculated joins) but of course you
still are tied to the semantics of the table structure.  Some
database libraries offer prepared queries, but AFAIK it is just
generating a stored proc behind the scenes, so this would not help
you with MySQL.

I agree.  Without stored procedures, MySQL cannot reach the level of
performance neccessary to win me over to using a SQL back-end.  The
abstraction argument is valid, but it's also possible to wrap DB
operations in a layer of code that would similarly abstract things.

Sean


_______________________________________________
MUD-Dev mailing list
MUD-Dev at kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev