pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: PGAccess/pgplsql Blues
Date: Mon, 09 Jul 2001 13:07:39 -0700
Message-ID: <web-82989@davinci.ethosmedia.com> (raw)
In-Reply-To: <200107091909.f69J9ff12430@candle.pha.pa.us>

Bruce,

      Thanks for checking that.   You actually missed the beginning of
the issue; it only crops up with long, complex functions > 100 lines
including nested text quoting.

      I'm getting out of the habit of using PGAccess for anything but
table lookups, anyway, so it's not worth it to me to hunt down the
issue.

-Josh

> 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, Pennsylvania
> 19026

______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



view thread (6+ messages)

Message-ID: <web-82989@davinci.ethosmedia.com>
Permalink:  ../web-82989@davinci.ethosmedia.com/
Also on:    postgresql.org/message-id/web-82989@davinci.ethosmedia.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: josh@agliodbs.com, pgman@candle.pha.pa.us
  Subject: Re: PGAccess/pgplsql Blues
  In-Reply-To: <web-82989@davinci.ethosmedia.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox