Re: plpgsql at what point does the knowledge of the query come in?

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-20 21:31:48
Message-ID: CAAtgU9QPgSceguOOLDzT7HSdmEf+WVK3F5VG4+w3g2GpQ-Y9Xg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 20, 2011 at 4:57 PM, Raymond O'Donnell <rod(at)iol(dot)ie> wrote:

>
>
> Not sure what you mean by the above...
>
> Ray.
>
>
This is what I thought it was doing.
1. it gets the node from the first row
2. measures its length
3. then loops through removing one character at a time and comparing that
to the whole column/query
4. for threeee it found a match in threee

then the function starts over for the next row

1. it gets the node from the second row
2. measures the length of the string
3. then loopse ....
4. ...

so it is the step 2 that looks like is not getting reset with each new
nnodetestt(node) in the select statement when it calls the function.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joe Abbate 2011-10-20 21:41:47 Re: how to disable all pkey/fkey constraints globally
Previous Message Henry Drexler 2011-10-20 21:13:04 Re: plpgsql at what point does the knowledge of the query come in?