Dear All
thank you for your quick response and support.
The example I have attached was just for help to illustrate problem and is
not so important.
I expected firebird to create in such situation the following check in the
backgroud:
ALTER TABLE LOCATION ADD CONSTRAINT CHK1_LOCATION C
>> Let's create two unites from one lot:
>>
>> INSERT INTO UNITES (CODE, LOT, SITE, DESCRIPTION) VALUES ('A1', 'L1', 'S1',
>> 'abc'); INSERT INTO UNITES (CODE, LOT, SITE, DESCRIPTION) VALUES ('A2',
>> 'L1', 'S1', 'bcd');
>>
>> I expected that the following instruction will not be exectued:
>> IN
> Let's create two unites from one lot:
>
> INSERT INTO UNITES (CODE, LOT, SITE, DESCRIPTION) VALUES ('A1', 'L1', 'S1',
> 'abc'); INSERT INTO UNITES (CODE, LOT, SITE, DESCRIPTION) VALUES ('A2',
> 'L1', 'S1', 'bcd');
>
> I expected that the following instruction will not be exectued:
> INSERT IN
Hi,
this is the feature – key is only valid(checked) for values but null is not
“value”.
This work same in all databases i have worked.
regards,
Karol Bieniaszewski
From: Paweł Świerzko p_swier...@poczta.onet.pl [firebird-support]
Sent: Wednesday, August 9, 2017 3:21 PM
To: firebird-support@ya
