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 CAAtgU9QPgSceguOOLDzT7HSdmEf+WVK3F5VG4+w3g2GpQ-Y9Xg@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>)
Responses Re: plpgsql at what point does the knowledge of the query come in?  (Raymond O'Donnell <rod@iol.ie>)
List pgsql-general

On Thu, Oct 20, 2011 at 4:57 PM, Raymond O'Donnell <rod@iol.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.


pgsql-general by date:

Previous
From: Henry Drexler
Date:
Subject: Re: plpgsql at what point does the knowledge of the query come in?
Next
From: Raymond O'Donnell
Date:
Subject: Re: plpgsql at what point does the knowledge of the query come in?