pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
PGAccess/pgplsql Blues
6+ messages / 4 participants
[nested] [flat]

* PGAccess/pgplsql Blues
@ 2001-06-01 16:30 Josh Berkus <josh@agliodbs.com>
  2001-06-01 17:28 ` Re: PGAccess/pgplsql Blues Tom Lane <tgl@sss.pgh.pa.us>
  2001-06-01 21:53 ` Re: PGAccess/pgplsql Blues Roberto Mello <rmello@cc.usu.edu>
  0 siblings, 2 replies; 6+ messages in thread

From: Josh Berkus @ 2001-06-01 16:30 UTC (permalink / raw)
  To: pgsql-sql

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



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: PGAccess/pgplsql Blues
  2001-06-01 16:30 PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
@ 2001-06-01 17:28 ` Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 0 replies; 6+ messages in thread

From: Tom Lane @ 2001-06-01 17:28 UTC (permalink / raw)
  To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-sql

"Josh Berkus" <josh@agliodbs.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



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: PGAccess/pgplsql Blues
  2001-06-01 16:30 PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
@ 2001-06-01 21:53 ` Roberto Mello <rmello@cc.usu.edu>
  2001-06-04 18:02   ` Re: PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
  1 sibling, 1 reply; 6+ messages in thread

From: Roberto Mello @ 2001-06-01 21:53 UTC (permalink / raw)
  To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-sql

On Fri, Jun 01, 2001 at 09:30:40AM -0700, Josh Berkus wrote:
> 
> 	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 ""'

	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. 

	-Roberto
-- 
+----| http://fslc.usu.edu USU Free Software & GNU/Linux Club |------+
  Roberto Mello - Computer Science, USU - http://www.brasileiro.net 
       http://www.sdl.usu.edu - Space Dynamics Lab, Developer    
I'm only a droid and not very knowledgeable about such things.



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: PGAccess/pgplsql Blues
  2001-06-01 16:30 PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
  2001-06-01 21:53 ` Re: PGAccess/pgplsql Blues Roberto Mello <rmello@cc.usu.edu>
@ 2001-06-04 18:02   ` Josh Berkus <josh@agliodbs.com>
  2001-07-09 19:09     ` Re: PGAccess/pgplsql Blues Bruce Momjian <pgman@candle.pha.pa.us>
  0 siblings, 1 reply; 6+ messages in thread

From: Josh Berkus @ 2001-06-04 18:02 UTC (permalink / raw)
  To: pgsql-sql

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



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: PGAccess/pgplsql Blues
  2001-06-01 16:30 PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
  2001-06-01 21:53 ` Re: PGAccess/pgplsql Blues Roberto Mello <rmello@cc.usu.edu>
  2001-06-04 18:02   ` Re: PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
@ 2001-07-09 19:09     ` Bruce Momjian <pgman@candle.pha.pa.us>
  2001-07-09 20:07       ` Re: PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Bruce Momjian @ 2001-07-09 19:09 UTC (permalink / raw)
  To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-sql


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



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: PGAccess/pgplsql Blues
  2001-06-01 16:30 PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
  2001-06-01 21:53 ` Re: PGAccess/pgplsql Blues Roberto Mello <rmello@cc.usu.edu>
  2001-06-04 18:02   ` Re: PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
  2001-07-09 19:09     ` Re: PGAccess/pgplsql Blues Bruce Momjian <pgman@candle.pha.pa.us>
@ 2001-07-09 20:07       ` Josh Berkus <josh@agliodbs.com>
  0 siblings, 0 replies; 6+ messages in thread

From: Josh Berkus @ 2001-07-09 20:07 UTC (permalink / raw)
  To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: pgsql-sql

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



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2001-07-09 20:07 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-06-01 16:30 PGAccess/pgplsql Blues Josh Berkus <josh@agliodbs.com>
2001-06-01 17:28 ` Tom Lane <tgl@sss.pgh.pa.us>
2001-06-01 21:53 ` Roberto Mello <rmello@cc.usu.edu>
2001-06-04 18:02   ` Josh Berkus <josh@agliodbs.com>
2001-07-09 19:09     ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-07-09 20:07       ` Josh Berkus <josh@agliodbs.com>

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