Re: Subject: Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread stan
On Mon, Aug 12, 2019 at 10:40:20AM -0700, Adrian Klaver wrote: > On 8/12/19 10:30 AM, stan wrote: > > > > The task_instance table is the one the original question was in > > > > reference > > > > to. > > > > > > > > CREATE TABLE employee ( > > > > employee_keyinteger DEFAULT >

Re: Subject: Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread Adrian Klaver
On 8/12/19 10:30 AM, stan wrote: The task_instance table is the one the original question was in reference to. CREATE TABLE employee ( employee_keyinteger DEFAULT nextval('employee_key_serial') PRIMARY KEY , id varchar(5) NOT NULL UNIQUE ,

Re: Subject: Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread stan
On Mon, Aug 12, 2019 at 10:16:41AM -0700, Adrian Klaver wrote: > On 8/12/19 10:06 AM, stan wrote: > > Cc: pgsql-general.lists.postgresql@panix.com > > Subject: Re: constrain with MATCH full and NULL values in referenced table > > User-Agent: Mutt/1.12.1 (2019-06-1

Re: Subject: Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread Adrian Klaver
On 8/12/19 10:06 AM, stan wrote: Cc: pgsql-general.lists.postgresql@panix.com Subject: Re: constrain with MATCH full and NULL values in referenced table User-Agent: Mutt/1.12.1 (2019-06-15) X-Editor: gVim On Mon, Aug 12, 2019 at 06:22:54PM +0200, Francisco Olarte wrote: Stan: On Mon, Aug

Subject: Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread stan
Cc: pgsql-general.lists.postgresql@panix.com Subject: Re: constrain with MATCH full and NULL values in referenced table User-Agent: Mutt/1.12.1 (2019-06-15) X-Editor: gVim On Mon, Aug 12, 2019 at 06:22:54PM +0200, Francisco Olarte wrote: > Stan: > > On Mon, Aug 12, 2019 at 5:1

Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread Francisco Olarte
Stan: On Mon, Aug 12, 2019 at 5:11 PM stan wrote: > > I am creating a table that has 2 values in it which are keys pointing to 2 > other tables. I need for the UNIQUE combination of these 2 keys to exist in > a fourth table. It has been recommended to use a foreign key constraint with > the MATCH

Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread Adrian Klaver
On 8/12/19 8:51 AM, stan wrote: Please reply to list also. Ccing list. On Mon, Aug 12, 2019 at 08:17:33AM -0700, Adrian Klaver wrote: On 8/12/19 8:11 AM, stan wrote: I am creating a table that has 2 values in it which are keys pointing to 2 other tables. I need for the UNIQUE combination of th

Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread Tom Lane
stan writes: > I am creating a table that has 2 values in it which are keys pointing to 2 > other tables. I need for the UNIQUE combination of these 2 keys to exist in > a fourth table. It has been recommended to use a foreign key constraint with > the MATCH FULL parameter. > Here is my question,

Re: constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread Adrian Klaver
On 8/12/19 8:11 AM, stan wrote: I am creating a table that has 2 values in it which are keys pointing to 2 other tables. I need for the UNIQUE combination of these 2 keys to exist in a fourth table. It has been recommended to use a foreign key constraint with the MATCH FULL parameter. Without t

constrain with MATCH full and NULL values in referenced table

2019-08-12 Thread stan
I am creating a table that has 2 values in it which are keys pointing to 2 other tables. I need for the UNIQUE combination of these 2 keys to exist in a fourth table. It has been recommended to use a foreign key constraint with the MATCH FULL parameter. Here is my question, does this deal with NU