> Robert Klemme wrote : > > > > >Hi all, > > > >I can't seem to get this to work: > > > >create dbproc XXX > >as > >var > > str VARCHAR(100); > >begin > > set str = 'FOO;'; > > execute 'drop dbproc CR_ADMIN.RR_' || str; > > stop($rc, $errmsg); > >end; > > > >Calling this SP results in a syntax error: > >Syntax error or access violation;-3005 POS(1) Invalid SQL statement. > > > >MaxDB version is 7.5.0 > > > >The error disappears if I comment the "stop" line so I assume > >it's a message > >resulting from the "execute". Anything I'm doing wrong here? > > > >Btw: stored procedures do not show up in SYS.CAT and > >SYS.ALL_OBJECTS. Is > >there any way to determine all stored procedures of a user > >programmatically? > > > >Thanks! > > > >Regards > > > >robert > > > > Please change > > set str = 'FOO;'; > > to > > set str = 'FOO'; > > since the semicolon is not part of the DROP DBPROC statement.
I should have mentioned that I did that already (in fact that was the original version) but with no effect. Same error message. Thx! robert > > HTH, > Thomas > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > -- +++ Jetzt WLAN-Router f�r alle DSL-Einsteiger und Wechsler +++ GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
