Re: plpgsql at what point does the knowledge of the query come in? - Mailing list pgsql-general

From Henry Drexler
Subject Re: plpgsql at what point does the knowledge of the query come in?
Date
Msg-id CAAtgU9TbMvd=VocDWPcCzC9MAa-QG2kCXjP-F3padv71sbifew@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql at what point does the knowledge of the query come in?  (Raymond O'Donnell <rod@iol.ie>)
List pgsql-general
When I was doing the mockups in excel using mid as a substitute for postgres substitute, I had to do -1 but that was actually not necessary as it was shorting the values, so the corrected plpgsql has the line

nnlength := length(newnode);
instead of nnlength := length(newnode)-1;

On Fri, Oct 21, 2011 at 6:10 AM, Raymond O'Donnell <rod@iol.ie> wrote:
On 20/10/2011 23:16, Henry Drexler wrote:
>
>
> On Thu, Oct 20, 2011 at 5:41 PM, Raymond O'Donnell <rod@iol.ie
> <mailto:rod@iol.ie>> wrote:
>
>
>     Are you sure about this? Try using RAISE NOTICE statements in the
>     function to output the value of nnlength each time it's executed.
>
>     Ray.
>
>
> Thank you for showing me the 'Rase Notice' , I had not seen that before
> and it helped me solve my problem right away.

Glad you got sorted. What was the problem in the end?

Ray.


--
Raymond O'Donnell :: Galway :: Ireland
rod@iol.ie

pgsql-general by date:

Previous
From: Yoann Moreau
Date:
Subject: GIN : Working with term positions
Next
From: Craig Ringer
Date:
Subject: Re: PostGIS in a commercial project