X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8B599567EC for ; Mon, 14 Mar 2005 18:29:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 15683-03 for ; Mon, 14 Mar 2005 18:29:08 +0000 (GMT) Received: from bramble.mmrd.com (bramble.mmrd.com [65.217.53.66]) by svr1.postgresql.org (Postfix) with ESMTP id ABC5F567E4 for ; Mon, 14 Mar 2005 18:29:06 +0000 (GMT) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by bramble.mmrd.com (8.12.8/8.12.8) with ESMTP id j2EI2BoJ027140; Mon, 14 Mar 2005 13:02:11 -0500 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [10.225.10.110]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id j2EISZJ15293; Mon, 14 Mar 2005 13:28:38 -0500 Received: from camel.mmrd.com ([172.25.5.213]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id 12GR2343; Mon, 14 Mar 2005 13:28:33 -0500 Subject: Re: column name is "LIMIT" From: Robert Treat To: Christopher Kings-Lynne Cc: Gourish Singbal , Russell Smith , pgsql-performance@postgresql.org In-Reply-To: <42355185.3070803@familyhealth.com.au> References: <674d1f8a0503132314754df153@mail.gmail.com> <200503141825.22827.mr-russ@pws.com.au> <674d1f8a05031400482c413087@mail.gmail.com> <42355185.3070803@familyhealth.com.au> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 14 Mar 2005 13:28:34 -0500 Message-Id: <1110824915.4281.123.camel@camel> Mime-Version: 1.0 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.04 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/272 X-Sequence-Number: 10977 Yeah... how come no one told him "don't do that"? LIMIT is an SQL reserved word, so it's likely to cause trouble in any database you try to use it on... I'd strongly recommend renaming that column asap. You can see other reserved words at http://www.postgresql.org/docs/8.0/interactive/sql-keywords-appendix.html Robert Treat On Mon, 2005-03-14 at 03:55, Christopher Kings-Lynne wrote: > You will still need to use double quotes in 8.0.1... > > Chris > > Gourish Singbal wrote: > > Thanks a lot, > > > > we might be upgrading to 8.0.1 soon.. till than using double quotes > > should be fine. > > > > regards > > gourish > > > > On Mon, 14 Mar 2005 18:25:22 +1100, Russell Smith wrote: > > > >>On Mon, 14 Mar 2005 06:14 pm, Gourish Singbal wrote: > >> > >>>Guys, > >>> > >>>I am having a problem firing queries on one of the tables which is > >>>having "limit" as the column name. > >>> > >>>If a run an insert/select/update command on that table i get the below error. > >>> > >>>ERROR: syntax error at or near "limit" at character 71 > >> > >>select "limit" from limit_table WHERE "limit" < 50 LIMIT 2; > >> > >>You need to quote the field name, and make sure the case is correct. > >> > >>>Any Help would be realyl great to solve the problem. > >>> > >>>postgresql 7.4.5 and linux OS > >>> > >> > >>You should probably upgrade to 7.4.7 > >> > >>Regards > >> > >>Russell Smith. > >> > > > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL