HP3000-L Archives

August 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Sletten Kenneth W KPWA <[log in to unmask]>
Reply To:
Sletten Kenneth W KPWA <[log in to unmask]>
Date:
Wed, 9 Aug 2000 16:40:53 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
[log in to unmask] astutely noted:

> This looks like the same problem I ran into recently. One of
> your column names is an Allbase reserved word. Here's the
> relevant section of the explanation I got from HP Support.
> Hope this helps.
>
> A SELECT of a column where the column name is an
> ALLBASE reserved word will fail, usually with a syntax error,
> DBERR 1001.  This can be avoided by using a table prefix

Another "good thing" HP could do to proactively avoid the above
"downstream" problem is to implement one of the "Medium effort"
enhancements on the current SIGIMAGE Enhancement Ballot:

"DBSCHEMA:  Flag ALLBASE reserved words with WARNing
(no restrictions now).  Would catch conflicts up-front, instead
of only later if IMAGE database is ATTACHed to a DBE".

Credits on above to Stan, who AFAIK was the first person to
submit this enhancement request to SIGIMAGE....

Ken Sletten
SIGIMAGE Chair

ATOM RSS1 RSS2