Comments on: Recursive SQL error

By: TomLiotta

TomLiotta — Thu, 14 Feb 2013 03:35:30 +0000

Yeah, it’s tricky when reviewing questions that are updated. I’m also not sure where the UPDATE line in the came from. Very possibly, it was a line that I failed to replace when I pasted into a temporary Notepad doc I was using.

But if “SQL statement not allowed” was original error text, then the ‘Answer’ is almost certainly correct. A SELECT statement is not meaningful as a RUNSQLSTM statement.

Tom

By: carlosdl

carlosdl — Wed, 13 Feb 2013 22:19:00 +0000

But that update doesn’t make much sense (at least to me), unless it is a separate statement. Could it be that Tom was testing something else, and included that line here by mistake? (not likely, I know).

By: philpl1jb

philpl1jb — Wed, 13 Feb 2013 18:04:00 +0000

Right I listed the SQL code as it appeared originally .. at that time it included an error statement but no
UPDATE TSTSQL/TSTTBL SET NAMECOL = ‘THIRD’ WHERE IDCOL = 3
Edited twice is suspect .. once adding the update and subsequently removing it.

By: carlosdl

carlosdl — Wed, 13 Feb 2013 15:09:43 +0000

Tom, what I don’t know is where you saw that it was an update

It seems that the question has been editted since I first saw it. Originally it included an error message.

By: TomLiotta

TomLiotta — Wed, 13 Feb 2013 00:23:22 +0000

And it’s also not clear why the editor often inserts
tags in code but the tags don’t get rendered when shown in browsers; but that’s separate from the actual ‘Question’. — Tom

By: TomLiotta

TomLiotta — Wed, 13 Feb 2013 00:19:24 +0000

Actual SQL appears to look this way (and I hope formatting works):

UPDATE TSTSQL/TSTTBL SET NAMECOL = ‘THIRD’ WHERE IDCOL = 3
 WITH RPL (LEVEL, PINBR, CINBR, QTYPR) AS
      (SELECT 1, ROOT.PINBR, ROOT.CINBR, ROOT.QTYPR
              FROM ITSTRU ROOT
              WHERE ROOT.PINBR = ’8B714-0005651′
       UNION ALL
             SELECT PARENT.LEVEL+1, CHILD.PINBR, CHILD.CINBR, CHILD.QTYPR
               FROM RPL PARENT, ITSTRU CHILD
             WHERE PARENT.CINBR = CHILD.PINBR
                AND PARENT.LEVEL < 2
      )
 SELECT PINBR, LEVEL, CINBR, QTYPR
        FROM RPL;

But I’m not clear on a couple things. First thing that I don’t see is how carlosdl knew what the error message was. I don’t see any mention of an error message, only that some problem exists.

Next, I can see why RUNSQLSTM would be a possibility; but it could also be a QM query. With no explanation of what is being attempted nor what any problem is, it’s impossible to say much.

Tom

By: philpl1jb

philpl1jb — Tue, 12 Feb 2013 22:45:59 +0000

I think this is the SQL but that's as far as I can go.

WITH RPL (LEVEL, PINBR, CINBR, QTYPR) AS 

(SELECT 1, ROOT.PINBR, ROOT.CINBR, ROOT.QTYPR 
FROM ITSTRU ROOT 
WHERE ROOT.PINBR = '8B714-0005651' 

UNION ALL 

SELECT PARENT.LEVEL+1, CHILD.PINBR, CHILD.CINBR, CHILD.QTYPR 
FROM RPL PARENT, ITSTRU CHILD 
WHERE PARENT.CINBR = CHILD.PINBR 
AND PARENT.LEVEL < 2 ) 

SELECT PINBR, LEVEL, CINBR, QTYPR FROM RPL;

By: carlosdl

carlosdl — Tue, 12 Feb 2013 21:36:24 +0000

Not sure who the author of the above answer is, but the answer makes sense, since the error message reads “SQL statement not allowed”.

Additionally, I’m not sure if the OP is intending to use the word LEVEL as a reserved word. If that is the case, that could be a problem, as AFAIK the LEVEL keyword is only allowed on hierarchical queries, which as far as I remember must include the CONNECT BY clause. (I might not remember well. though)