Filter doesn't work properly on float number

michellenweiter · Post by **michellenweiter** » Wed 08 Apr 2009 13:56

Hello,

The TOraQuery (and maybe other ODAC componants) seems to have a bug when you filter using the OraQuery.filter := myFloat on float values.

For some unknown reasons, certain values can't be found when filtered by them, like 165.744.

If I use an ADOQuery Componant, instead of ODAC, with the same database and query, it works fine. Also if I use Toad or SQL Plus, it works.

We use D2005, ODAC 6.70.0.45 and Oracle 10GR2.

Thanks
michel

Plash · Post by **Plash** » Thu 09 Apr 2009 07:38

I have replied you by e-mail.

michellenweiter · Post by **michellenweiter** » Thu 09 Apr 2009 08:13

Hello,

I tried to set the EnableNumbers option of TOraSession to True, but it doesn't solve the problem.

Thanks
michel

Plash · Post by **Plash** » Thu 16 Apr 2009 07:11

We could not reproduce the problem. Please send to odac*devart*com a complete small sample that demonstrates the problem, including the script for creating database objects.

michellenweiter · Post by **michellenweiter** » Mon 20 Apr 2009 12:18

The problem is really easy to reproduce:

MyOraQuery.sql := 'select 165.744 as s_km from dual';
MyOraQuery.filter := 's_km = 165.744';
MyOraQuery.Open;

You will have no rows back!

Thanks a lot for your solution.
michel

Plash · Post by **Plash** » Tue 21 Apr 2009 07:14

We could not reproduce the problem. Please specify your version of Oracle client and server.

michellenweiter · Post by **michellenweiter** » Tue 21 Apr 2009 09:07

we do not use and need Oracle client since we use the ODAC NET version. The Oracle version is 10.2.0.1.0 und 10.2.0.3.0 (we have this problem on both)
(my local Oracle client is 10.2.0.1.0)

Plash · Post by **Plash** » Tue 21 Apr 2009 09:19

We have reproduced the problem with the Direct mode, and we are working on it. You will be notified when we fix the problem.

michellenweiter · Post by **michellenweiter** » Tue 21 Apr 2009 09:26

What can help you a lot: if I disable the NET option (and go over the Oracle Client) then it seems to work. But we can't and don't want to install the Oracle Client everywhere. That's why we choosed the ODAC NET product.