Thanks very much for the response, Gerd. But I already have ";" set as
the statement separator. (If I didn't, then maybe DB2 would be throwing
a syntax error on the ";" character?)
Again, the problem isn't the ";", but rather the line feed. It looks
from here like what Squirrel is doing is just stripping out the ";", but
then sending the entire block - including line feeds - to db2 all at
once, rather than breaking it into separate statements like you
described below.
That doesn't seem to be a problem with any of the other DB's I've worked
with, but apparently DB2 has a problem with it. Doesn't seem to be any
way to tweak this in Squirrel (or DB2) that I can see, though,
unfortunately.
Anyway, thanks for the suggestion. Looks like I'm stuck with executing
one statement at a time for now though. Ugh. If anything else comes to
mind, please do let me know.
Thanks,
DR
Gerd Wagner wrote:
> Hi David,
>
> I couldn't reproduce your problem on my UDB 8.2. No matter what I set
> SQuirreL's statement separator to. My UDB 8.2 itself seems to accept ';'
> as statement separator.
>
> The pointer I can give you is to check SQuirreL's statement separator.
> See Session Properties --> Tab SQL --> Statement Separator. If you set
> the separator to ';' and execute
>
> UPDATE foo SET bar = 5;
> UPDATE home SET bart = 3;
>
> SQuirreL should send the following two statements to your DB:
>
> 1. UPDATE foo SET bar = 5
> 2. UPDATE home SET bart = 3
>
> (Note, no ';' at the end.) The DB should be able to execute these
> statements.
>
> Hope it helps.
>
> Gerd
|