Received: from mout02.kundenserver.de (mout02.kundenserver.de [195.20.224.133]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBLLHm642002 for ; Thu, 21 Dec 2000 16:17:48 -0500 (EST) (envelope-from zuschlag2@online.de) Received: from [195.20.224.75] (helo=mrelay00.kundenserver.de) by mout02.kundenserver.de with esmtp (Exim 2.12 #2) id 149D5g-0000Ot-00 for Pgsql-interfaces@postgresql.org; Thu, 21 Dec 2000 22:17:32 +0100 Received: from p3e9eaecd.dip0.t-ipconnect.de ([62.158.174.205] helo=jozu) by mrelay00.kundenserver.de with smtp (Exim 2.12 #2) id 149D5E-00045j-00 for Pgsql-interfaces@postgresql.org; Thu, 21 Dec 2000 22:17:04 +0100 From: "Johann Zuschlag" To: "Pgsql-interfaces@postgresql.org" Date: Thu, 21 Dec 2000 22:17:58 +0100 Reply-To: "Johann Zuschlag" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: keyword LIMIT in SQL-statement, psqlodbc workaround? Message-Id: X-Archive-Number: 200012/202 X-Sequence-Number: 548 Hi, I'm using a commercial application. Well, apart from the problem that it crashes my psqlodbc.dll (which I'm trying to debug) it uses the keyword LIMIT. Like: CREATE ITEMS (NAME VARCHAR(10), LIMIT NUMERIC... To my knowledge it worked with PostgreSQL 6.4. Why not with 7.x? I thought it should be possible. Did I misinterpret SQL-92/98? MS-SQL and ORACLE are accepting it. Since I can't persuade my application to put LIMIT in quotes, I need another solution. Any ideas, workarounds how to do it in psqlodbc? regards Johann