=?UTF-8?Q?Rafa=C5=82_Rzepecki?= divided.m...@gmail.com writes:
I'm pretty sure the original intent was to afford some extra checks so
that conditions such as ROW(1, 2) IN ((ROW(3, 4), ROW(5, 6, 7))
would get rejected at parsing time (CCing the original author; please
confirm).
No; the reason
On Wed, Jun 5, 2013 at 7:58 AM, Amit Kapila amit.kap...@huawei.com wrote:
On Wednesday, June 05, 2013 5:34 AM Rafał Rzepecki wrote:
On Tue, Jun 4, 2013 at 12:35 PM, Amit Kapila amit.kap...@huawei.com
wrote:
On Saturday, June 01, 2013 9:37 PM
Row type literals constructed with ROW() cause
On Wednesday, June 05, 2013 5:34 AM Rafał Rzepecki wrote:
On Tue, Jun 4, 2013 at 12:35 PM, Amit Kapila amit.kap...@huawei.com
wrote:
On Saturday, June 01, 2013 9:37 PM
Row type literals constructed with ROW() cause an error when used in
an IN clause (string literals casted appropriately
On Saturday, June 01, 2013 9:37 PM
Row type literals constructed with ROW() cause an error when used in an
IN
clause (string literals casted appropriately are allowed). This is
especially problematic since many client libraries use these literals
to
pass values of row-type arguments,
On Tue, Jun 4, 2013 at 12:35 PM, Amit Kapila amit.kap...@huawei.com wrote:
On Saturday, June 01, 2013 9:37 PM
Row type literals constructed with ROW() cause an error when used in an
IN
clause (string literals casted appropriately are allowed). This is
especially problematic since many client
The following bug has been logged on the website:
Bug reference: 8198
Logged by: Rafal Rzepecki
Email address: divided.m...@gmail.com
PostgreSQL version: 9.2.4
Operating system: Ubuntu 13.04
Description:
Row type literals constructed with ROW() cause an error when
