Re: Having more than one constraint trigger on a table

2019-10-24 Thread Andreas Joseph Krogh
På torsdag 24. oktober 2019 kl. 16:59:42, skrev Adrian Klaver < adrian.kla...@aklaver.com >: On 10/22/19 8:26 AM, Andreas Joseph Krogh wrote: > På tirsdag 22. oktober 2019 kl. 17:12:59, skrev Adrian Klaver > mailto:adrian.kla...@aklaver.com>>: > > [snip] >

Re: Having more than one constraint trigger on a table

2019-10-24 Thread Adrian Klaver
On 10/22/19 8:26 AM, Andreas Joseph Krogh wrote: På tirsdag 22. oktober 2019 kl. 17:12:59, skrev Adrian Klaver mailto:adrian.kla...@aklaver.com>>: [snip] No. When I sort the triggers I get: test=# create table trg_str(fld_1 varchar); CREATE TABLE test=# insert into

Re: Having more than one constraint trigger on a table

2019-10-22 Thread Andreas Joseph Krogh
På tirsdag 22. oktober 2019 kl. 17:12:59, skrev Adrian Klaver < adrian.kla...@aklaver.com >: [snip] No. When I sort the triggers I get: test=# create table trg_str(fld_1 varchar); CREATE TABLE test=# insert into trg_str values ('trigger_1_update_fts'),

Re: Having more than one constraint trigger on a table

2019-10-22 Thread Adrian Klaver
On 10/22/19 7:54 AM, Andreas Joseph Krogh wrote: Hi. I have the following schema (question at bottom): == CREATE TABLE company(idSERIAL PRIMARY KEY, parent_idINTEGER REFERENCES company(id)DEFERRABLE INITIALLY DEFERRED ,name VARCHAR NOT NULL, duns_numberVARCHAR,

Having more than one constraint trigger on a table

2019-10-22 Thread Andreas Joseph Krogh
Hi. I have the following schema (question at bottom): == CREATE TABLE company(id SERIAL PRIMARY KEY, parent_id INTEGER REFERENCES company(id) DEFERRABLE INITIALLY DEFERRED , name VARCHAR NOT NULL, duns_number VARCHAR, fts_all tsvector, t_updated BOOLEAN); CREATE