Firebird: Error Invalid request BLR after upgrade from 6.3.13, to 6.4.14

[Giovanna]

After upgrade from 6.3.13, to 6.4.14, with Delphi XE2, I'm getting an error when I insert a record with generator:
Invalid request BLR at offset 68
generator ID_CORIV is not defined

I use a TUniTable with GeneratorMode=gmInsert,
I have any problem if change with GeneratorMode=gmPost

Regards,
Giovanna Cellitti

[Giovanna]

I noticed with the 6.3.13 version, that the same error it was only visible through DBMonitor, before the 6.3.13 version there was no error
Regards,
Giovanna Cellitti

[ViktorV]

In order to get a detailed answer, please compose a small sample demonstrating the described behavior and send it to viktorv*devart*com, scripts for creating database objects. In addition, please specify the exact server version.

[ViktorV]

This is a correct error returned by the server. It occurs due to that you have specified a non-existing ID_CORIV generator in the KeyGenerator property. To solve the issue, please specify a correct name ID_CORIV_GEN in the TUniConnection.SpecificOptions.Values['KeyGenerator'] property.

[Giovanna]

Why if I set GeneratorMode=gmPost it don't generate the error with the same key generator?
And why in the previous version it worked?
Best regards,
Giovanna Cellitti

[ViktorV]

In your sample, you are getting the specified error, when the GeneratorMode property is set to gmPost, because you are explicitly assign a value for the ID_CORIV field in the OnStateChange event handler of the TDataSource component. In this case, when the GeneratorMode property is set to gmPost, the assigned value will be used. To get the same behavior on any GeneratorMode value, you should comment out the following line in your code:

Code: Select all

  CoRivID_CORIV.AsInteger := 0;

During investigation, your sample worked the same with both UniDAC 6.3.14 and UniDAC 6.3.13. Please check your sample functioning on the same Firebird version when using UniDAC 6.3.14 and UniDAC 6.3.13 and let us know the result.

[Giovanna]

I send you the same sample compiled with Unidac release 6.3.13, only with DbMonitor it's possible see the error, in addition the record is any case insert.
Best regards,
Giovanna Cellitti

[ViktorV]

Thank you for the information. We have reproduced the issue and investigation is in progress. We will inform you when we have any results.