| From: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
|---|---|
| To: | Geoff Winkless <pgsqladmin(at)geoff(dot)dj> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Alexandre GRAIL <postgresql(dot)general(at)augure(dot)net>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Casting Integer to Boolean in assignment |
| Date: | 2019-01-24 15:36:13 |
| Message-ID: | CAEzk6fepSm-ywhOGx6QCWmaWqoq00MfVcnu5T27_+ScMjRzWRw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 24 Jan 2019 at 15:32, Geoff Winkless <pgsqladmin(at)geoff(dot)dj> wrote:
> DELETE FROM <tablename> WHERE <integer>;
>
> What would you be thinking that that ought to do?
To be fair, I suppose that accidentally missing out a test but
including an integer field
DELETE FROM <tablename> WHERE <integerfieldname>;
could do this. Not something I've ever done, but at least I see how
it's possible.
*shrug* I should reiterate, it's just my opinion, I'm certainly not
arguing for it to be changed, although I would be pretty upset if the
existing ability to change the behaviour were removed.
Geoff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-01-24 15:40:33 | Re: Casting Integer to Boolean in assignment |
| Previous Message | Geoff Winkless | 2019-01-24 15:32:03 | Re: Casting Integer to Boolean in assignment |