Vlad Khorsun
Vlad Khorsun
> > Note, `updateRecord()` should not put blob into log if it was not changed. > > What it will do if the record is not found on the target...
> > Note, `updateRecord()` should not put blob into log if it was not changed. Thus it should have a bit different code. I can prepare a patch with such...
> > > Note, `updateRecord()` should not put blob into log if it was not changed. > > > > > > What it will do if the record is...
> Do you have on mind a next update with still unchanged BLOB value? Dumb question, isn't is ?
What version of firebird.msg does the program use (see) ?
Or: does application uses firebird.msg at all ? These messages were never included into firebird.dll and exists in firebird.msg only. (never == since v2.5 at least).
> > if `compileRelation()` called more than once for the single query - how many times `idl_count` will be incremented ? > > `compileRelation()` is called from `Optimizer::compile()`, and `Optimizer::checkIndices()`...
Note comment in `Statement::Statement()`: > relation locks MUST be taken before index locks It become more complex than it looks
Provide full status-vector or minimal reproducible test case. EDS uses common way to interprete status-vector, so I doubt it directly related. I see that `safe_interpret()` considers `isc_arg_sql_state` as 'always first'...
I failed to find any docs re isc_arg_sql_state. It was introduced in 2.5 and backported from Vulcan, AFAIU. Consider to prepare the patch for safe_interpret(), or change your status-vector as...