Re: Reality check on PFs created as SQL TABLEs

On 6/10/26 11:19 AM, Rob Berendt wrote:
> If by "more than one inherent key field" do you mean a key on an order
> detail file by order# and line#?  You just have to do it right.  Instead of
> putting the PRIMARY KEY on an individual column you put it at the end.
> CONSTRAINT iim_pri_key PRIMARY KEY (Order_number, order_line)

Fascinating. Actually, the "CONSTRAINT iim_pri_key" part is optional, at 
least in DB2 on a Midrange box and it seems that Stefan's syntax would 
have worked, if only I'd set it off from the last field with a comma. 
And sure enough, I found an example (albeit *with* the CONSTRAINT 
<name>) in *SQL for Dummies* (which, so far as I'm aware is based on 
MySQL and M$ Access).

At any rate, the new tool I'm adding to QuestView hasn't yet balked at 
anything I've thrown at it.

--
JHHL
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support-FMtJrHiV//lnDLsaKlm4mFaTQe2KTcn/@public.gmane.org for any subscription related questions.