Skip site navigation (1) Skip section navigation (2)

Re: BUG #5974: UNION construct type cast gives poor error message

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Mike Fowler" <mike(at)mlfowler(dot)com>
Cc: "Jeff Wu" <jwu(at)atlassian(dot)com>,<pgsql-bugs(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #5974: UNION construct type cast gives poor error message
Date: 2011-04-14 21:28:40
Message-ID: 4DA720B8020000250003C856@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-bugs
Mike Fowler <mike(at)mlfowler(dot)com> wrote:
 
> So to summarise, Oracle and PostgreSQL need minor tweaks to run
> cleanly and SQLServer and MySQL do not.
 
The FROM DUAL in Oracle has nothing to do with the issue at hand. 
That is just because they always require a FROM clause on every
SELECT.  DUAL is a special table with one row you can use when you
just want to select a literal.
 
That means that all three of the databases you tested have
extensions to the standard similar to what is being contemplated for
PostgreSQL.  If nothing else, adding such an extension would ease
migration from those other products, but I think it would prevent
some user confusion and posts to the -bugs list, too.
 
-Kevin

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2011-04-14 21:48:00
Subject: Re: BUG #5974: UNION construct type cast gives poor error message
Previous:From: qintaoDate: 2011-04-14 20:57:12
Subject: BUG #5979: postgres service cannot be started if database is located in NAS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group