Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 10 total
Thread Error reporting during a SQL Script
Sat, Apr 5 2008 4:32 PMPermanent Link

Dan Rootham
Tim,

Using EDBMgr ver 1.08 Build 1

When running a long script I may get an error like this:
[ ElevateDB Error #401 The column SortTranslit does not exist ]

In ver 2 of EDBMgr, it would be really helpful to see a script line number when
hitting an error like this. It would help greatly with the debugging and correction,
because the same column name may appear many times in the script. Mostly
the column exists, but for one table it doesn't. The line number would nail it !

Thanks,
Dan
Sat, Apr 5 2008 4:56 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Dan,

<< When running a long script I may get an error like this:
[ ElevateDB Error #401 The column SortTranslit does not exist ]

In ver 2 of EDBMgr, it would be really helpful to see a script line number
when hitting an error like this. It would help greatly with the debugging
and correction, because the same column name may appear many times in the
script. Mostly the column exists, but for one table it doesn't. The line
number would nail it ! >>

I'll see what I can do, but it's a little more difficult than it seems from
the outside.  These type of errors occur in the deep insides of the catalog
object handling code, and don't really have a point of reference in terms of
the the currently-executing script.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Apr 5 2008 5:03 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Dan,

<< When running a long script I may get an error like this:
[ ElevateDB Error #401 The column SortTranslit does not exist ] >>

After looking at this for a few minutes, I'm a bit puzzled as to the context
in which you got this error message.  For which statement in the script did
you see this error message without a line and column number ?

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Apr 5 2008 6:38 PMPermanent Link

Dan Rootham
Tim,

<< After looking at this for a few minutes, I'm a bit puzzled as to the context
in which you got this error message.  For which statement in the script did
you see this error message without a line and column number ? >>

Here are a few lines extracted from the script. I have marked the errored
line with  "<<<<<".

SCRIPT
BEGIN
. . . . preceding statements . . . .
EXECUTE IMMEDIATE
 'ALTER TABLE "Dict_Chi"
  ALTER COLUMN "Term" AS VARCHAR(100) COLLATE CHS';
EXECUTE IMMEDIATE
 'ALTER TABLE "Dict_Chi"
  ALTER COLUMN "SortField" AS VARCHAR(20) COLLATE CHS';
EXECUTE IMMEDIATE          <<<<< fails here: col "SortTranslit" doesn't exist
 'ALTER TABLE "Dict_Chi"
  ALTER COLUMN "SortTranslit" AS VARCHAR(20) COLLATE ENU_CI';
EXECUTE IMMEDIATE
 'CREATE INDEX "AlphaIndex" ON "Dict_Chi" ("SortField" COLLATE CHS)';
. . .   following statements after this . . . .
END

To check this point I have re-run a similar errored script, and the line/column
number is not reported. Hope this info helps?

Regards,
Dan
Sun, Apr 6 2008 5:32 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


Would it be possible to report the table name for that bit of the script? Most of the time that would be enough for me.

Roy Lambert
Sun, Apr 6 2008 5:39 AMPermanent Link

Dan Rootham
Roy,

<< Would it be possible to report the table name for that bit of the script?
Most of the time that would be enough for me. >>

Yes, that would be enough to resolve where the problem lies.

Dan
Mon, Apr 7 2008 2:17 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Dan,

<< Here are a few lines extracted from the script. I have marked the errored
line with  "<<<<<". >>

Okay, I've got where the issue is.  Anything not caught during the
compilation is missing the line and column information.   This type of
information has to wait until execution because it relies on being
"lock-covered" to ensure that the information is not invalid due to
time/duration issues.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Apr 8 2008 8:20 AMPermanent Link

Dan Rootham
Tim,

"<< Anything not caught during the compilation is missing the line
and column information. >>

Understood. And presumably you can't report the statement being executed,
because it might be way too long to use in an error message?

Thanks,
Dan
Tue, Apr 8 2008 2:49 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Dan,

<< Understood. And presumably you can't report the statement being executed,
because it might be way too long to use in an error message? >>

Sure, but we can still report the line and column information, and that's
what I've done for 1.09 B2.  The EDB Manager puts the cursor right on the
statement with the error now. Smiley

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Apr 9 2008 4:04 AMPermanent Link

Dan Rootham
Tim,

<< we can still report the line and column information, and that's
what I've done for 1.09 B2. >>

Thank you, that's great.

<< The EDB Manager puts the cursor right on the statement
with the error now. Smiley>>

Aaahh.... yes. Apologies!

Regards,
Dan
Image