Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f51GUiE64468 for ; Fri, 1 Jun 2001 12:30:44 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 65768 for ; Fri, 01 Jun 2001 09:30:40 -0700 From: "Josh Berkus" Subject: PGAccess/pgplsql Blues To: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Fri, 01 Jun 2001 09:30:40 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200106/6 X-Sequence-Number: 3209 Folks, I've been having an annoying problem that I'm hoping someone else has had and solved: When I edit some of my more complex plpgsql functions using PGAccess, the functions break and cannot be made to work again except by reloading them from PLSQL/text. All attempts to use the function after PGAccess editing are met with: 'Parse error at or near ""' Once the *identical* function text is reloaded via PSQL command-line, however, the function works. I'm using Postgres 7.1 RC2 and PGAccess 0.98.5. -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco