Subject Re: Prepared Statement and UDF
Author Roman Rokytskyy
Hi,

> We are using 1.0. To your knowledge, is there any existing problem with
> trying to use a UDF in a prepared statement like this? Is it a known
> limitation of 1.0.3 or should we able to do this? Any other syntax we
> could try besides an unprepared statement? I'm wondering if the
> unquoted column parameter is the issue.

I talked with Dmitry Yemanov about this. He says that it should work,
and if it doesn't, he would like to have a look. I found that the same
exception I get in following statements:

SELECT * FROM rdb$database WHERE upper(?) = ?
SELECT * FROM rdb$database WHERE ascii_val(upper(?)) = 65

However, without upper(...) these statements work. If you have
reproducable test case, please send it to me or to Dmitry directly.

Roman