Running the query in IB_SQL succeeds, but perhaps too well:
insert into contact
(kCont,fkres,emFirst)
Values(-1,26,'Julie')
Primary key value setting is taken literally, when in fact what is desired is to generate the next key value, 1 in this case.
Hosting package developer gave me the default value for PK of -1, which is intended to activate the generator to provide the next available PK value.
From creation script for this table:
CREATE GENERATOR GENCONTACTNO;
SET GENERATOR GENCONTACTNO TO 0;
CREATE TABLE CONTACT (
KCONT INTEGER NOT NULL, /*etc.*/
UPDATE RDB$RELATION_FIELDS SET RDB$DESCRIPTION = 'pk="autoincrement" label="##" type="hidden"' WHERE (RDB$RELATION_NAME = 'CONTACT') AND (RDB$FIELD_NAME = 'KCONT');
ALTER TABLE CONTACT ADD CONSTRAINT RESIDENTS_CONTACT
FOREIGN KEY (FKRES) REFERENCES RESIDENTS (KRES);
=============
Running the query in Delphi generates following error
Violation of Primary or Unique key constraint "INTEG_17" on table "CONTACT".
Don't know how to interpret that. Does INTEG_17 refer to the PK or FK contraint?
Comments appreciated.