"Invalid BLOB ID" in IBX insert operation [CORE1417]

[firebird-automations]

Submitted by: michalk1 (michalk1)

Attachments: InsBlob.zip

When executing two subsequent insert operations into a blob field, first one with arbitrary not null value and the second one with null value, "Invalid BLOB ID" error arises on condition that transaction is restarted between the two calls. It seems (my presumption) that when parameter is assigned a null value, IBX just sets some flag and leaves rest of the parameter structure intact, which allows the old "BLOB ID" to survive to the next call. Unlike previous Firebird versions, FB2.1 Beta1 probably tests validity of the "BLOB ID" even if the parameter contains null value, which fails after commit of the original transaction.

CREATE TABLE TESTTAB ( MEMOFLD BLOB CHARACTER SET ASCII );

Tsc.StartTransaction; Ibsql.SQL.Text := 'INSERT INTO TESTTAB (MEMOFLD) VALUES (:MEMOFLD)'; Ibsql.ParamByName('MEMOFLD').AsString := 'AAA'; // any not null value Ibsql.ExecQuery; Tsc.Commit;

Tsc.StartTransaction; Ibsql.ParamByName('MEMOFLD').Clear; // null value Ibsql.ExecQuery; // "Invalid BLOB ID" raised here Tsc.Commit;

The same code runs ok if - ran against FB1.5 or FB2.0 OR - inserts are executed within the same transaction OR - CHARACTER SET is not specified in field definiton

Commits: FirebirdSQL/firebird@0b76787f198ba973d0a3dd53922bfd0b9230a55d

[firebird-automations]

Modified by: @dyemanov

assignee: Adriano dos Santos Fernandes \[ asfernandes \]

[firebird-automations]

Commented by: Sean Leyne (seanleyne)

IBX does not directly support Firebird, never has.

v2.1 contains changes to the treatment/definition of Blob's at the API level, which is the likely why the application no longer runs correctly.

You are advised to:

- investigate other database connection components (IBObjects or FIBPlus), or - use the older FBClient/GDS32 DLLs for your client application

[firebird-automations]

Commented by: @asfernandes

No, Sean!

There is already a similar problem using .Net Provider, but I wasn't able to reproduce it using fbclient.

[firebird-automations]

Commented by: @asfernandes

Michal, could you please attach here a simple test case, that I can configure database location to test?

[firebird-automations]

Commented by: michalk1 (michalk1)

Test case application

[firebird-automations]

Modified by: michalk1 (michalk1)

Attachment: InsBlob\.zip \[ 10530 \]

[firebird-automations]

Commented by: michalk1 (michalk1)

Sean, I know that IBX officially doesn't support Firebird and in long term its better to switch to a different component set, but so far it works ok. After all, IBX gurantees support of older interbase versions and FB API is said to be backward compatible as well, so theoretically this could work as long as I don't use new FB features. Since Delphi includes IBX sources, it is also possible to build modified IBX version.

Change of client library (IBX uses GDS32.DLL) doesn't help, the exception is still raised.

Adriano, I attached a test case. Just run the exe file, fill in database name, click at "Create Db" (once) and then at "Run insert". This should lead to the exception in FB2.1 Beta1.

[firebird-automations]

Commented by: @asfernandes

Thanks for the test case.

[firebird-automations]

Modified by: @asfernandes

status: Open \[ 1 \] =\> Resolved \[ 5 \] resolution: Fixed \[ 1 \] Fix Version: 2\.1 Beta 2 \[ 10190 \]

[firebird-automations]

Modified by: @pcisar

status: Resolved \[ 5 \] =\> Closed \[ 6 \]

[firebird-automations]

Modified by: @pcisar

Workflow: jira \[ 12850 \] =\> Firebird \[ 14621 \]

[firebird-automations]

Modified by: @pavel-zotov

QA Status: No test

[firebird-automations]

Modified by: @pavel-zotov

status: Closed \[ 6 \] =\> Closed \[ 6 \] QA Status: No test =\> Cannot be tested