Thanks Tom. I rid the NULLs and altered all uniqueidentifier functions to
strict and everything worked fine.
>From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>To: "T- Bone" <jbowen333(at)hotmail(dot)com>
>CC: pgsql-novice(at)postgresql(dot)org, dmitry(at)taurussoft(dot)org
>Subject: Re: [NOVICE] Simple function closes connection to server Date:
>Mon, 11 Apr 2005 12:37:28 -0400
>"T- Bone" <jbowen333(at)hotmail(dot)com> writes:
> > However, when I execute it as follows, my connection to the db gets
> > and, obviously, there is no result. In fact, it appears that ALL
> > connections are closed (this is not good).
> > SELECT "ZoneID", "getZoneName"("ZoneID"::text) AS "ZoneName"
> > FROM "tblOrganisation";
>Do you have any NULL entries in the ZoneID column? It looks to me like
>the uniqueidentifier package fails to declare its functions as STRICT,
>and since most of them aren't actually coded to check for null input
>values, they'll crash on nulls. In particular uniqueidentifier_text
>My recommendation would be to mark all those functions as strict
>(and get rid of the tests for null input that do exist in a couple).
> regards, tom lane
Powerful Parental Controls Let your child discover the best the Internet has
Start enjoying all the benefits of MSN Premium right now and get the
first two months FREE*.
In response to
pgsql-novice by date
|Next:||From: Cima||Date: 2005-04-15 22:42:40|
|Subject: oids as primary keys?|
|Previous:||From: Andres Ledesma||Date: 2005-04-15 19:26:51|
|Subject: Re: oids as primary keys?|