Tim

Once I am able to actually use a function something that would be really nice would be to know wether its the first time for that sql statement the function has been called, wether its somewhere in the midst of the rows to be scanned or its on the last row.

This occurred to whilst writing the TEXTSEARCH stuff. The words to search going in are going to be consistent throughout the search. Since I don't know where I am in the process I have to parse the list each time. Its not going to take long, and compared with parsing the field to be checked it will probably be trivial but it would be good to be able to parse these words once at the beginning of the search and then do a bit of housekeeping afterwards. The ability to do that would make some of my DBISAM custom filters when translated much faster.

I know I can set up a variable to say the initial setups been done. What I'm stuck on is how to determine when to do the housekeeping at the end.


Roy Lambert

Tim


I worked out that I would also need a unique identifier for each TEXTSEARCH in a query otherwise I'm limited to only one.

I doubt this is easily doable

Roy Lambert

Roy,

<< Once I am able to actually use a function something that would be really
nice would be to know wether its the first time for that sql statement the
function has been called, wether its somewhere in the midst of the rows to
be scanned or its on the last row.

This occurred to whilst writing the TEXTSEARCH stuff. The words to search
going in are going to be consistent throughout the search. Since I don't
know where I am in the process I have to parse the list each time. Its not
going to take long, and compared with parsing the field to be checked it
will probably be trivial but it would be good to be able to parse these
words once at the beginning of the search and then do a bit of housekeeping
afterwards. The ability to do that would make some of my DBISAM custom
filters when translated much faster.

I know I can set up a variable to say the initial setups been done. What
I'm stuck on is how to determine when to do the housekeeping at the end. >>

EDB really doesn't even know this information at the level where the
functions are called, so it really isn't possible to pass any information on
to you.  Functions are intended to be simply used as a one-off in all
instances.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


OK. It was a bit of a forlorn hope anyway.


Roy Lambert