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 m
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
> > "standa
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 work
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
> editin
"Josh Berkus" <[EMAIL PROTECTED]> 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
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 t
