Martin,
I've seen a problem with BASE TABLE STRUCTURE caused by the fact that
that is, for the parser, a triple keyword. The parse problem caused the
syntax to be accepted/rejected based on whether there was white space
or ; after the word STRUCTURE. This is a bug, of course, and has been
fixed. IIRC this was in Ingres r3, so maybe not applicable to your
issue, but since no one else is taking the bait ... ;)
MikeT

Signature
Michael Touloumtzis
Ingres Development
Computer Associates
Hi Mike,
Not quite right, but pretty close. I raised the problem with the local Tech
Support and this is what they found...
The constraint is okay if you use index="BASE TABLE STRUCTURE"
Note the Double Quotes.
However, and this is a beaut! - Having put the constraint in place an
attempt to copy the table with copydb generates a SIGSEGV.
rat.ingres> copydb rep_dest CURRENT_NAME
INGRES COPYDB Copyright 2003 Computer Associates Intl, Inc.
Unload directory is '/usr1/install/ingres/Replicator/test_1'.
Reload directory is '/usr1/install/ingres/Replicator/test_1'.
There is one table owned by user 'INGRES'.
Exiting . . .
due to
Segmentation Violation (SIGSEGV)
@PC=3ff800d8bd4,PS=8,PV=3ff800d8b80,GP=14000dd90,SP=11fffb2
30,VFP=11fffb230,RA=12001684c,v0=11fffb738
a0-5[0,1,0,1400044b9,0,140004142]
t0-
11[80,0,11fffb75e,0,0,11fffb75c,7f,1,22203d20584544,0,42,45534142]
s0-5[11fffb640,11fffb738,4,140005a18,0,140004488]
Please contact your Technical Support representative.
Segmentation fault
Isnt that fun!
Marty
--
Random Duckman Quote #102:
Cornfed: Uh Oh.
Duckman: 'Uh Oh' as in 'Nice Work?'
Cornfed: No, as in 'You're screwed.'