sign function return error!

Discussion of open issues, suggestions and bugs regarding IBDAC (InterBase Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
xalion
Posts: 124
Joined: Fri 20 May 2005 10:08

sign function return error!

Post by xalion » Tue 06 May 2008 09:54

SQL:
select b.*,case
when b.xx0 then 'xx2'
when b.xx=0 then 'xx3'
end "xxxx" ,sign(xx) as sj
from gzb b

the return value of sj is: 0,1 ,-256.
-256 shoud be -1.

please fix it!

xalion
Posts: 124
Joined: Fri 20 May 2005 10:08

Post by xalion » Wed 07 May 2008 03:53

in Ibdac 2.5 beta ,it works ok!

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Wed 07 May 2008 07:47

Please specify whether SIGN is your own function. If so, please provide the code of this function.

Also specify the exact version of your Firebird or InterBase server, and the exact version of IBDAC (with the build number) where the problem occurs.

xalion
Posts: 124
Joined: Fri 20 May 2005 10:08

Post by xalion » Wed 07 May 2008 07:57

database server:Firebird 2.1
Ibdac version: 2.20.2.15
delphi 2007
sign function is firebird builder-in funtion.

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Thu 08 May 2008 07:29

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

xalion
Posts: 124
Joined: Fri 20 May 2005 10:08

Post by xalion » Mon 12 May 2008 09:07

I send the sample project and database to you.
Do you check it?

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Mon 12 May 2008 13:07

We have received your sample project. Could you please create another sample project without using national characters in the SQL property ?

xalion
Posts: 124
Joined: Fri 20 May 2005 10:08

Post by xalion » Tue 13 May 2008 07:07

I resend it to you as your requird!

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Tue 13 May 2008 08:59

We have reproduced the problem. Next IBDAC build will be based on IBDAC 2.50 beta. So the problem will be fixed there.

Post Reply