Charles Bainbridge wrote:

"Ian, Yusauf, 2.30b1 includes a fix to a problem around STANDARD NULL BEHAVIOUR=False reported on December 4th 2018 (by Yusuf). Are you saying there's still a problem with STANDARD NULL BEHAVIOUR=False? We have chosen to use =False as we have so much old DBISAM (and Paradox before that) code that assumes empty string and NULL are equivalent, our system breaks badly if we run with STANDARD NULL etc. enabled."


Hi Charles,
yes in latest version there is a bigger bug than in version before. Now if "STANDARD NULL BEHAVIOUR" is disabled, queries like "select * from mytable where mystringfield='' and vmodul=0" are note resulting rows, but without vmodul=0 i get a result ... the problem is that all rows have the vmodul field filled with 0 and not with null.
the fix in 2.30b1 is a fix for mystringfield='' ... it results all rows where mystringfield is null or is '' but if field (like vmodul) has a value (in my example 0) i can't filter ... Tim knows this and hopefully will provide a bugfix in the next days ...

Yusuf Zorlu
MicrotronX

If you work with "STANDARD NULL BEHAVIOUR" = FALSE
i would not update to 2.30b1 !!

Yusuf Zorlu
MicrotronX

Yusuf

Thanks for this pointer! I will hold off until Tim has got round to a fix.

Charles,

<< Ian, Yusauf, 2.30b1 includes a fix to a problem around STANDARD NULL BEHAVIOUR=False reported on December 4th 2018 (by Yusuf). Are you saying there's still a problem with STANDARD NULL BEHAVIOUR=False? We have chosen to use =False as we have so much old DBISAM (and Paradox before that) code that assumes empty string and NULL are equivalent, our system breaks badly if we run with STANDARD NULL etc. enabled. >>

Yes, there's still an issue.  The fix in December fixed string columns, but apparently there's still an issue with non-string columns.  I'm trying to get a fix out by early next week.

Tim Young
Elevate Software
www.elevatesoft.com