Joe schrieb:
I guess I wasn't clear enough. Currently, I'm about to use the native
Win32 port. I suspect pgsql-hackers-win32 subscribers won't
appreciate newbie-type questions. Specifically, I installed 8.0.3
with the installer. Then I opened a command prompt window, typed
'createdb mydb'
David Lazar <[EMAIL PROTECTED]> writes:
> ERROR: RETURN cannot have a parameter in function returning set; use
> RETURN NEXT at or near "pkg" at character 1149
> Did something change from pgsql 7.X series set returning function to
> version 8.X series???
I think 8.0 actually complains that you
Hi,
I run a function that returns a setof custom type rows against pgsql
7.4.6 and it works great. The same type and function was migrated to
pgsql 8.0.3 but fails to run, returning an error:
ERROR: RETURN cannot have a parameter in function returning set; use
RETURN NEXT at or near "pkg" at
Jeff Gold <[EMAIL PROTECTED]> writes:
> [ backend memory leak ]
Found it --- the actual leak is in index_create, not in TRUNCATE or
CLUSTER at all; and it's been there a really long time.
Patch for 7.4 branch attached.
regards, tom lane
Index: index.c
> > I've made a PL/pgSQL function to validate UPC and EAN barcodes.
> > It works correctly, but is a little ugly.
> > Wondering if any PL/pgSQL experts can offer some suggestions. (I'm
> > new to PL/pgSQL.)
For what it's worth, here's a function I'm using to calculate the checksum of
an EAN barc
Miles Keaton presumably uttered the following on 06/25/05 01:44:
I've made a PL/pgSQL function to validate UPC and EAN barcodes.
It works correctly, but is a little ugly.
Wondering if any PL/pgSQL experts can offer some suggestions. (I'm
new to PL/pgSQL.)
Main questions:
#1 - I wanted to ad
