MVSFORUMS.com

SMS · Beginner Joined: 16 Oct 2005 Posts: 53 Topics: 24

Hi,

I tried to create the referential constraint as follows.

FIELD1 INTEGER NOT NULL WITH DEFAULT
CONSTRAINT D_FIELD1
REFERENCES T1.TABLE1 (FIELD1)
ON DELETE CASCADE ON INSERT RESTRICT,

But I am getting the below error.

DSNT408I SQLCODE = -199, ERROR: ILLEGAL USE OF KEYWORD INSERT. TOKEN KEY WAS
EXPECTED

When I remove the 'ON INSERT RESTRICT' it works fine. Please help me on this. I wonder whether DB2 V8 supports ON INSERT / UPDATE referential constraints.

Really this forum was very useful. Couple of times the response I got from here was very helpful at the crucial times. Thanks.

Regards,
SMS

CraigG

videlord · Beginner Joined: 09 Dec 2004 Posts: 147 Topics: 19

check the manual, SQL reference, you'll get the answer.
Do not build your own SQL

SMS · Beginner Joined: 16 Oct 2005 Posts: 53 Topics: 24

If you look into the below URL, it talks about the referential integrity for insert & update. Though it's for version 9, long time back I have read about the insert & update referential constraints in the earlier versions. But I could not find that manual.

http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.ibm.db29.doc.intro/db2z_db2enforcesreferentialconstraints.htm

Thanks,
SMS

CraigG · Posted: Mon Nov 12, 2007 12:50 pm Post subject:

SMS · Beginner Joined: 16 Oct 2005 Posts: 53 Topics: 24

I already read that topic. Actually I found an example with ON DELETE RESTRICT ON UPDATE RESTRICT, so I thought there were some explicit Insert / Update constraints and was trying to find the syntax. But now only I realize that I wrongly read the example from IBM UDB for Iseries.

Now I am clear. I can create triggers for my requirements. Thanks for your help.

Regards,
SMS