Albert and JM,
Be wary about using CASCADE. I tried it once and have not been able to
turn it off
where used on that database.
At 14:44 20/04/01 -0500, you wrote:
>JM, because you have overtyped, R:Base thinks you have changed the value.
>try
>ALTER TABLE...SET CASCADE
>and see if you can then change it. It will also uppercase all the lower
>table values as well. You may want to turn cascade off again when you are
>done.
>
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>Behalf Of J.M. GRATIAS
>Sent: Friday, April 20, 2001 1:13 PM
>To: Rbase List server
>Subject: Q. about Constraints
>
>
>
>Hi all,
>
>I have a main table with a PK KeyName TEXT 4
>and a secondary table with a FK (same name and same definition) that
>reference KeyName.
>
>The code is alphanumeric and have been entered in lower cases.
>
>When I try to retype the PK in Uppercase, I get the constraint message
>saying that the PK value can't be changed because it is referenced in an
>other table.
>
>As CASE is set to OFF, I don't understand why ...
>
>Same with :
>
>UPDATE MainTableName SET KeyName = (LUC(Keyname)) WHERE KeyName =
>'KeyValue'
>
>I find this feature much more strict than it should be ....
>And also unlogical, because :
>
>UPDATE SecondaryTableName SET KeyName = (LUC(Keyname)) WHERE KeyName =
>'KeyValue'
>works fine ... but :
>UPDATE MainTableName SET KeyName = (LUC(Keyname)) WHERE KeyName =
>'KeyValue'
>still don't work, and without any reason ...
>
>Is there a way to turn that off (without deleting the constraint of course)
>?
>
>TIA
>
>J.M. GRATIAS, Logimatique, France
Warmest regards,
Tom Grimshaw
coy: Just For You Software
tel: 61 (0)2 9552 3311
fax: 61 (0)2 9566 2164
email: [EMAIL PROTECTED]
mobile: 0414 675 903
street: 3/66 Wentworth Park Rd Glebe NSW 2037
post: PO Box 470 Glebe NSW 2037 Australia
_/_/_/_/_/_/_/_/ _/_/_/_/_/_/ _/ _/ _/_/_/_/_/
_/ _/ _/ _/ _/
_/ _/ _/ _/ _/
_/ _/_/_/_/ _/ _/_/_/_/_/
_/ _/ _/ _/
_/ _/ _/ _/ _/
_/ _/ _/ _/_/_/_/_/
