From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | andrei(at)ivc(dot)com |
Subject: | BUG #15055: parenthesis disappear |
Date: | 2018-02-07 16:04:37 |
Message-ID: | 151801947737.1240.172380540503895826@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15055
Logged by: Andrei Mitran
Email address: andrei(at)ivc(dot)com
PostgreSQL version: 9.6.1
Operating system: centos
Description:
alter table ivc.merit_matches
add constraint priced_or_slotted_job
check ((survey_code is null and slot_job_code is not null) or
(slot_job_code is null and survey_code is not null));
results in:
Check constraints:
"priced_or_slotted_job" CHECK (survey_code IS NULL AND slot_job_code IS
NOT NULL OR slot_job_code IS NULL AND survey_code IS NOT NULL)
What happened to my parens around the and conditions? I am not aware of any
precedence of and over or - Am i misinformed?
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2018-02-07 16:05:07 | Re: BUG #15053: SIGSEGV - While executing query with cube agregator |
Previous Message | David G. Johnston | 2018-02-07 14:51:34 | Re: BUG #15054: intermittent error: An I/O error occured while sending to the backend. |