Hello Mart�n,
concerning the stored procedure capabilities of SQL studio
you wrote :
> I see some inconveniences:
>
> 1. The text of the stored procedure is not kept as
> entered but instead is translated to uppercase
>
> 2. I have to manually drop the procedure before I save the
> changes and there 's no way to have a piece of SQL
> that says "if exists drop it and then create it"
> (...)
> Also, SQL Studio is just for
> Win32 clients. Any consensus on how to do it in unix ?
to 1. : the uppercasing of the stopro text is done in the
database kernel during execution of the 'create dbproc'
statement, and this will probably not change in the near future.
All you can do here is to enclose your _identifiers_ in double
quotes
to prevent them from being uppercased.
to 2. : unfortunately there is no such construction as 'if exists'
in plain SQL as you would submit it from SQL Studio.
if you prefer to have a development cycle like this
a) edit some kind of script file which embeds a conditional 'drop dbproc'
and a 'create dbproc' statement.
b) run it
c) test the dbproc
d) goto a)
you could e.g. consider the python api of replication manager (see the
docs);
for the condition you could use sth like
> select count(*) from dbprocedures where dbprocname = 'theNameOfYourProc'
<
regards,
Markus Stausberg
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
