Received: from mout03.kundenserver.de (mout03.kundenserver.de [195.20.224.218]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBSCHCL01800 for ; Thu, 28 Dec 2000 07:17:12 -0500 (EST) (envelope-from zuschlag2@online.de) Received: from [195.20.224.151] (helo=mrelay01.kundenserver.de) by mout03.kundenserver.de with esmtp (Exim 2.12 #2) id 14Bbzm-0001lq-00 for Pgsql-interfaces@postgresql.org; Thu, 28 Dec 2000 13:17:22 +0100 Received: from p3e9c20c4.dip0.t-ipconnect.de ([62.156.32.196] helo=jozu) by mrelay01.kundenserver.de with smtp (Exim 2.12 #2) id 14Bbzi-0007DR-00 for Pgsql-interfaces@postgresql.org; Thu, 28 Dec 2000 13:17:18 +0100 From: "Johann Zuschlag" To: "Pgsql-interfaces@postgresql.org" Date: Thu, 28 Dec 2000 13:16:02 +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: solved: keyword LIMIT in SQL-statement, psqlodbc workaround? Message-Id: X-Archive-Number: 200012/236 X-Sequence-Number: 582 On Thu, 21 Dec 2000 22:17:58 +0100, Johann Zuschlag wrote: >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... > I just added some very basic code in modul convert.c/copy_statement_with_parameters parsing for "Limit" and changing one letter. Is not really smart, but works for me. regards Johann