| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: PGAccess/pgplsql Blues |
| Date: | 2001-06-01 17:28:06 |
| Message-ID: | 3422.991416486@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"Josh Berkus" <josh(at)agliodbs(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Barrett | 2001-06-01 19:09:33 | seleting all dates between two dates |
| Previous Message | george young | 2001-06-01 16:36:41 | select distinct too slow |