Re: PGAccess/pgplsql Blues

FYI, I could not reproduce this problem in the current CVS sources.

I created a function 'select 1;' and saved it, then opened the function
and added a comment line, saved that, and it worked fine.

> Roberto,
> 
> >  IIRC, pgaccess does quote-escaping for you, so if you try to write
> > "standard" PL/pgSQL (escaping single quotes), it'll barf this error.
> > 
> >  Just something to check. 
> 
> Thanks.  This doesn't seem to be the case; it seems to be a translation
> problem:
> 
> 1. Test fn_save_order: it's working.
> 2. Open fn_save_order in PGAccess.
> 3. Add '--test comment' on its own line.
> 4. Save fn_save_order.
> 5. test it: "Parse Error at or near "" "
> 
> Unfortunately, I can't afford to pay Constatin for debugging, so that's
> where things stand ...
> 
> -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
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026