I have created an external function in dll. That function returns Boolean (actualy it does not really matter).
Function works just fine when I use it in SELECT statement. Something like that "SELECT MyFunction('SomeValue', MyTable.CLOBField1) as test FROM MyTable".
As the second parameter I use a field from the selected table. It suppost to be a value from a row. Which is good.
When I am trying to use the same function in WHERE clause it doesn't work. Debugging shows me that the second parameter is the same all the time (actually a column from the first row in
the table).

Do I have to use something like CURRENTROW.MyField (which is not an issue...just imagine)?

Please, give me a direction where to go to solve this.

Alec,

<< I have created an external function in dll. That function returns Boolean
(actualy it does not really matter).  Function works just fine when I use it
in SELECT statement. Something like that "SELECT MyFunction'SomeValue',
MyTable.CLOBField1) as test FROM MyTable".  As the second parameter I use a
field from the selected table. It suppost to be a value from a row. Which is
good. When I am trying to use the same function in WHERE clause it doesn't
work. Debugging shows me that the second parameter is the same all the time
(actually a column from the first row in the table). >>

It's an issue with EDB - if you request a sensitive result set or a filter,
then it will work fine.  However, an insensitive result set will exhibit the
issue.   A fix will be in 1.06 B2.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I have tried and it works with a sensitive result set.
I can stay with that until the next update.

Thank you


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Alec,

<< I have created an external function in dll. That function returns Boolean
(actualy it does not really matter).  Function works just fine when I use it
in SELECT statement. Something like that "SELECT MyFunction'SomeValue',
MyTable.CLOBField1) as test FROM MyTable".  As the second parameter I use a
field from the selected table. It suppost to be a value from a row. Which is
good. When I am trying to use the same function in WHERE clause it doesn't
work. Debugging shows me that the second parameter is the same all the time
(actually a column from the first row in the table). >>

It's an issue with EDB - if you request a sensitive result set or a filter,
then it will work fine.  However, an insensitive result set will exhibit the
issue.   A fix will be in 1.06 B2.

--
Tim Young
Elevate Software
www.elevatesoft.com