BUG #1313: problems with array syntax parsing in SQL statements

From: "PostgreSQL Bugs List" <pgsql-bugs(at)postgresql(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #1313: problems with array syntax parsing in SQL statements
Date: 2004-11-11 19:55:30
Message-ID: 20041111195530.9AB717388A2@www.postgresql.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 1313
Logged by: Pascal Pochet

Email address: postgresql(at)p3-consulting(dot)net

PostgreSQL version: 7.4.5

Operating system: Mac OS X

Description: problems with array syntax parsing in SQL statements

Details:

In INSERT statements the string '{}' is correctly parsed as an empty array
when '{ }' is not, as if the space was signifiant, and generates a syntax
error.

Also
'{"A", "B"}' will be correctly parsed when
'{"A", "B" }' (note the space before the closing brace ) will generate the
following entry '{"A","B "} : the space(s) between the latest double quote
and the closing brace is/are added to the latest item of the array.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2004-11-11 22:43:58 BUG #1314: STATEMENT_TIMEOUT DOES NOT WORK PROPERLY
Previous Message Josh Berkus 2004-11-11 17:55:35 Re: SELECT FOR UPDATE and LIMIT 1 behave oddly