Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f51HSME88585 for ; Fri, 1 Jun 2001 13:28:22 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f51HS7R03425; Fri, 1 Jun 2001 13:28:07 -0400 (EDT) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: PGAccess/pgplsql Blues In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Fri, 01 Jun 2001 09:30:40 -0700" Date: Fri, 01 Jun 2001 13:28:06 -0400 Message-ID: <3422.991416486@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/8 X-Sequence-Number: 3211 "Josh Berkus" writes: > 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 ""' Hmm, is it possible PGAccess is DOS-ifying the newlines? At one point I fixed plpgsql to accept DOS-style newlines, but maybe someone broke it again. Or maybe that's not the problem, but it's worth checking. regards, tom lane