| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | Michael Sacket <msacket(at)gammastream(dot)com> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: NULL value comparison |
| Date: | 2012-08-23 01:17:09 |
| Message-ID: | 50358495.1090807@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 08/22/2012 10:58 PM, Michael Sacket wrote:
> Thank you all very much!
>
> Unfortunately I can't change the query... but I can modify the data. I updated the NULL values to 'N' and put the appropriate NOT NULL constraint and a default value of 'N'.
What tool/app is generating the query? They need to be told they're
doing something wrong and unsafe - unless it's documented that the
target column must be NOT NULL, anyway.
PostgreSQL has a workaround for one such wrong, broken and unsafe
program, Microsoft Access. However the workaround is limited to
transforming "= NULL" to "IS NOT NULL"; it doesn't actually change the
semantics of NULL.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2012-08-23 01:42:31 | no null checking/check constraint checking in nested tables: Bug, missing feature, or desired behavior? |
| Previous Message | Craig Ringer | 2012-08-23 01:13:31 | Re: NULL value comparison |