Commented by: @asfernandes

We can do nothing without proper test case.

Commented by: flipo (zflipo)

I'm working on preparing test database and code to submit.

Commented by: Sean Leyne (seanleyne)

No, the "problem" may be solved with a later version of IBO, which you may need to update to. IBO bug are not a project responsibility.

Commented by: flipo (zflipo)

Just saw your post.

I was incorrect about TIB_CURSOR working.

I don't give much hope on this being resolved as changing one CONTAINING to LIKE fixes the issue while same
sql statement still contains similar CONTAINING against blobs works.

thanks for your quick responses.

Commented by: @AlexPeshkoff

Even with closed issue it seems that something may be wrong with 2.5.1. So - please prepare test case using our isql. This will save us all a lot of time, avoiding need to guess is it IBO or FB bug.

Commented by: Damyan Ivanov (dam)

I tried the following query in isql on LI-V2.5.2.26424 Firebird 2.5 (amd64, snapshot from the 2.5 release branch) and it worked:

SQL> select first 1 id from events where details containing 'max';

               ID 

=====================
24945011169

events.details is BLOB segment 80, subtype TEXT CHARACTER SET UNICODE_FSS Nullable

Commented by: flipo (zflipo)

OK,
I will send today offending fdb with some data.
Sorry for delay but pc decided to belly up yesterday.

Commented by: flipo (zflipo)

Given that tbInventory is a TIB_Query

tbInventory.sql.text:= 'Select Inventory.*,ItemComments.comments from Inventory Left Join ItemComments on ItemComments.GUID=Inventory.GUID where Inventory.Server=:Server and ((ItemComments.Comments CONTAINING :PLike0) or (Slayer CONTAINING :PLike0) or (ReqSkillName CONTAINING :PLike0) or (Itemname CONTAINING :PLike0) or (SpellNames CONTAINING :PLike0 ) or (SetNumber CONTAINING :PLike0 ) or (Cast(WieldReqAmount as VARCHAR(20) )=:P0) or (Cast(ArmourLevel as VARCHAR(20) ) = :P0) )'

..do setting of parameters.
execute returns only column headings.

If prior to execute I change the tbInventory.Sql via a call to a function which generate a new sql statment that utilizing that same tbInventory.sql.text and tbinventory.Sql.Params[x] executing that will provide data.

set tbInventory.sql.text as above and
do setting of parameters.

NewSql:=GetSQLWithParamData(tbInventory);

//newsql returns for my test 'Select Inventory.*,ItemComments.comments from Inventory Left Join ItemComments on ItemComments.GUID=Inventory.GUID where Inventory.Server='Solclaim' and ((ItemComments.Comments CONTAINING 'Key') or (Slayer CONTAINING 'Key') or (ReqSkillName CONTAINING 'Key') or (Itemname CONTAINING 'Key') or (SpellNames CONTAINING 'Key' ) or (SetNumber CONTAINING 'Key' ) or (Cast(WieldReqAmount as VARCHAR(20) )='Key') or (Cast(ArmourLevel as VARCHAR(20) ) = 'Key') )'

tbInventory.sql.text:=NewSql;
execute returns column headings and data.

Commented by: flipo (zflipo)

It appears that TBI_query is having trouble generating a valid sql statement based on what version of firebird.

I know that if you change just the following
(ItemComments.Comments CONTAINING 'Key')
to
(ItemComments.Comments LIKE '%Key%')
That the query is working again.

So yes something about Firebird 2.1.5 is causing IBO to have issues.

Given that a explicit sql statement works it points to IBO issue. Given that sql works against prior FB 2.1.5 it points to firebird.

Now i have to go figure out what is going on with users who upgraded to 2.1.5 and then reverted to 2.1.0 as they are reporting that a different query has stopped working.

Thanks for your effort. I've enjoyed blissful use of Firebird since the 1.x days.

Commented by: @AlexPeshkoff

Well, it looks like I've EXLICITLY written - do it using _isql_.