Search found 3 matches
- Mon Aug 28, 2017 8:25 am
- Forum: Report a Bug
- Topic: Key violation
- Replies: 6
- Views: 14869
Re: Key violation
That was fast work! It has fixed the problem for me. Thanks.
- Fri Aug 25, 2017 6:09 am
- Forum: Report a Bug
- Topic: Key violation
- Replies: 6
- Views: 14869
Re: Key violation
Thanks, D_INSERT does work as an alternative workaround. I'm more interested in reporting the bug than in finding workarounds. I wonder what other operations might also be affected if constraints aren't being enforced correctly.
- Thu Aug 24, 2017 8:48 pm
- Forum: Report a Bug
- Topic: Key violation
- Replies: 6
- Views: 14869
Key violation
V: 3.007, OS: Windows 10
When I declare multiple keys it appears that only the first of the keys is enforced.
VAR foo REAL RELATION {a INTEGER, b INTEGER} KEY {a} KEY {b};
INSERT foo RELATION {TUPLE {a 1, b 1}};
INSERT foo RELATION {TUPLE {a 2, b 1}};
result:
a b
1 1
2 1
When I declare multiple keys it appears that only the first of the keys is enforced.
VAR foo REAL RELATION {a INTEGER, b INTEGER} KEY {a} KEY {b};
INSERT foo RELATION {TUPLE {a 1, b 1}};
INSERT foo RELATION {TUPLE {a 2, b 1}};
result:
a b
1 1
2 1