From: | Henry Drexler <alonup8tb(at)gmail(dot)com> |
---|---|
To: | rod(at)iol(dot)ie |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: plpgsql at what point does the knowledge of the query come in? |
Date: | 2011-10-21 10:45:47 |
Message-ID: | CAAtgU9TbMvd=VocDWPcCzC9MAa-QG2kCXjP-F3padv71sbifew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)iol(dot)ie> wrote:
> On 20/10/2011 23:16, Henry Drexler wrote:
> >
> >
> > On Thu, Oct 20, 2011 at 5:41 PM, Raymond O'Donnell <rod(at)iol(dot)ie
> > <mailto:rod(at)iol(dot)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(at)iol(dot)ie
>
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Guether | 2011-10-21 13:05:11 | postgres/postgis eats memory |
Previous Message | Yoann Moreau | 2011-10-21 10:23:40 | GIN : Working with term positions |