I review only the procedure control statements, that is the main part of PSM
standard.

There are 10 procedure control statements in PSM. For a complete syntax and
description of each one you can find it in
http://developer.mimer.se/documentation/Mimer_SQL_Reference_Manual/SQL_State
ments10.html#1213697
SAPDB actually has 6 of the statements implemented: CALL, COMPOUND, IF
(partially), LEAVE (break), SET and WHILE
and need 4 more: CASE, LOOP, REPEAT and RETURN.

There are 5 more statements defined in PSM and that I don't include
previously, they are:

SIGNAL/RESIGNAL (a synonym of STOP)
http://developer.mimer.se/documentation/Mimer_SQL_Reference_Manual/SQL_State
ments7.html#1213692
DECLARE CONDITION (give a name to a SQLSTATE)
DECLARE HANDLER (similar to TRY/CATCH)
DECLARE VARIABLE (synonym of VAR)
http://developer.mimer.se/documentation/Mimer_SQL_Reference_Manual/SQL_State
ments6.html#1213689

Some databases has more than one procedure language, the syntax of the
CREATE PROCEDURE usually adds a LANGUAGE attribute, perhaps the best
solution is to define a new language ("PSM"") to create procedures, and
maintain the old one as a different one ("NATIVE").

Regards
Blas Rodriguez Somoza

----- Original Message -----
From: "Anhaus, Thomas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, February 06, 2002 9:32 AM
Subject: SQL/PSM (Why create dbproc?)


> Blas Rodriguez Somoza wrote
> >Up to the date, DB2, postgresql and interbase has complete SQL/PSM
support,
> whether Oracle claims that it PL/SQL is "similar" to PSM. Sybase and
> Microsoft follow
> >the TransactSQL and apparently don't want to support any ANSI/ISO
standard
> more than ANSI92-Entry.
> >Standards is good for all, but specially for Open Source projects,
because
> it makes easier to switch from one database to another.
> >I don't check the full SQL/PSM standard. But the following is a quick
list
> of what SAPDB lacks of
> >CREATE PROCEDURE (as a synonym to CREATE DBPROC) DROP PROCEDURE (as a
> synonym to DROP DBPROC)
> >LEAVE (as a synonym to BREAK)
> >ELSEIF clausule at IF.
> >CASE statement.
> >LOOP statement.
> >FOR statement.
> >If there is any interest in standards compliance, I think those
enhacements
> must be in the TODO list.
> >Does SAP want SAPDB to be standard compliant?
> Up to now SAPDB has no PSM standard support. If only the described
features
> have to be supported, I don't
> see any problems to fulfill the standard. I will take this into account
for
> the planned improvements of the
> procedure language.
> Thomas
> ---
> Thomas Anhaus
> SAPDB, SAP Labs Berlin
>
>
>

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to