| From: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: COALESCE and NULLIF semantics |
| Date: | 2009-09-11 17:29:09 |
| Message-ID: | 20090911172909.GQ5407@samason.me.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 11, 2009 at 06:24:22PM +0100, Sam Mason wrote:
> One thing I've just realized these discussions have pointed out is
> that PG isn't doing the correct thing all the time with types. When
> is it ever valid to see an "unknown" after type checking? AFAICT, it
> shouldn't ever appear and hence doing:
>
> CREATE VIEW v AS SELECT 'foo';
>
> Should be doing the normal default to TEXT type. Is that right? or does
> "unknown" have more meaning besides just being something that needs to
> be fixed up during type checking.
Doh, sorry I shouldn't have sent that. I wanted to spend some time to
see if I could find any other examples, but I hit send by accident.
--
Sam http://samason.me.uk/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-09-11 17:33:10 | Re: COALESCE and NULLIF semantics |
| Previous Message | Kevin Grittner | 2009-09-11 17:26:45 | Re: COALESCE and NULLIF semantics |