Certainly you can change this.
Edit the following file in your source tree:
[EMAIL PROTECTED]:/brownes/wolfe/compiles/pgsql> vi
src/include/pg_config_manual.h
/*
* Maximum number of columns in an index and maximum number of
* arguments to a function. They must be the same value.
*
* The min
On Thu, Feb 10, 2005 at 10:07:50AM -0800, David Fetter wrote:
>
> Short of recompiling as others have suggested, you could put large #
> of params into an array and have the function unwind that.
In 8.0 or later, you could also use a function that takes a single
parameter of a composite type and
On Wed, Feb 09, 2005 at 10:11:19PM -0500, Oisin Glynn wrote:
> Hi,
>
> I am trying to keep database access encapsulated in functions from an
> insert and update point of view so as all of the applications writing to
> the database are using the same functions/statements.
>
> My problem is I was
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] ("Oisin Glynn") would
write:
> I am trying to keep database access encapsulated in functions from an
> insert and update point of view so as all of the applications writing
> to the database are using the same functions/statements.
>
> My p
;
Sent: Wednesday, February 09, 2005 10:40 PM
Subject: RE: [GENERAL] Functions with more than 32 parameters
I just had the same problem the other day.
Change this file:
/postgresql-8.0.0/src/include/pg_config_manual.h
#define INDEX_MAX_KEYS 64 /*was 32 */
#define FUNC_MAX_ARGS
Hi,
I am trying to keep database access encapsulated in functions from an insert
and update point of view so as all of the applications writing to the
database are using the same functions/statements.
My problem is I was creating functions to do inserts/updates and now I have
a table with more
