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

Re: parse error: LIMIT combined with UNION

From: Steve Pothier <STEVEN(dot)POTHIER(at)saic(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: STEVEN(dot)POTHIER(at)saic(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: parse error: LIMIT combined with UNION
Date: 2001-09-07 14:06:08
Message-ID: 200109071406.f87E68U11019@payson.tucson.saic.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom,

You are correct. My humblest apologies.  When I did the test it was on
a machine not local to the database.  The client machine was running
psql 7.1 but the server is (apparently) 7.0.3.  I say "apparently"
because I'm not sure how to find the version of the server!  I just
assume that the server and psql client versions match on a specific
machine.

Sorry again for my lack of diligence in the "bug" report.

-sp-

   cc: pgsql-bugs(at)postgresql(dot)org
   Date: Thu, 06 Sep 2001 15:24:54 -0400
   From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>

   Steve Pothier <STEVEN(dot)POTHIER(at)saic(dot)com> writes:
   >   PostgreSQL version (example: PostgreSQL-6.5.1):   PosegreSQL 7.1

   > hbase=# SELECT * FROM subject WHERE subject_id LIKE '0009%' UNION (SELECT * FROM subject WHERE subject_id LIKE '0008%' LIMIT 5);
   > ERROR:  parser: parse error at or near "limit"

   Are you sure that's actually 7.1, and not some beta release?  The
   command parses fine for me in current sources and in 7.1.3.  AFAICT,
   the last time anyone changed LIMIT/sub-SELECT parsing was 2001-01-15,
   which would have been post 7.1-beta3.

			   regards, tom lane


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2001-09-07 14:18:05
Subject: Re: parse error: LIMIT combined with UNION
Previous:From: Tom LaneDate: 2001-09-07 13:49:47
Subject: Re: Odp: Huge view file

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