SQL/PSM (Why create dbproc?)

[Blas Rodriguez Somoza]

Hello       I don't know if the SAPDB procedure language follow the SQL/PSM standard, but I think it will be good to be as closest as posible.        The parameter passing and other statements of the procedure language seems to follow the standard, although thare are some statements included in the standard that SAPDB does not include (ELSEIF,CASE,LOOP,FOR) or include with a different speaking (BREAK in SAPDB/ LEAVE in SQL/PSM).       The main think that is different from the standard is the CREATE DBPROC/DROP DBPROC statements, when the usual ones is CREATE PROCEDURE/DROP PROCEDURE and this is the SQL/PSM standard syntax.       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?   Regards Blas Rodriguez Somoza