| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Transforming IN (...) to ORs, volatility |
| Date: | 2011-04-11 16:35:02 |
| Message-ID: | 4970.1302539702@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Does anyone object to making BETWEEN and IN more strict about the data
> types? At the moment, you can do this:
> postgres=# SELECT '1234' BETWEEN '10001'::text AND 10002::int4;
> ?column?
> ----------
> t
> (1 row)
> I'm thinking that it should throw an error. Same with IN, if the values
> in the IN-list can't be coerced to a common type.
You *will* get push-back on that ... maybe from people with badly coded
applications, but I guarantee there will be complaints.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2011-04-11 17:29:30 | Re: switch UNLOGGED to LOGGED |
| Previous Message | Marc G. Fournier | 2011-04-11 16:33:46 | Re: pgfoundry down? |