issue-#49 new fixes in SqlOdbc/3
Posted: Mon Apr 25, 2016 2:05 am
This is voting about issue-#49.
http://redmine.blackboxframework.org/issues/49
The discussion
ODBC deadlock problem in SqlOdbc and SqlOdbc3 was resolved completely.
The previous fix was a best effort (95%) work around but not a 100% fix.
When reading multiple parts of a column (ReadVarString, ReadBlob),
any DB operation must be suppressed until the column has been read completely.
Calling NEW in between can invoke the garbage collector, which in turn can finalize unused tables.
Finalization of tables has therefore been delayed by using an action.
Plus one trivial Optimization: empty and NULL VARCHAR strings reuse a common string object.
The BlackBox version for testing:
http://blackboxframework.org/unstable/i ... b1.515.zip
The suggested differences:
http://redmine.blackboxframework.org/pr ... ae881451b2
http://redmine.blackboxframework.org/issues/49
The discussion
ODBC deadlock problem in SqlOdbc and SqlOdbc3 was resolved completely.
The previous fix was a best effort (95%) work around but not a 100% fix.
When reading multiple parts of a column (ReadVarString, ReadBlob),
any DB operation must be suppressed until the column has been read completely.
Calling NEW in between can invoke the garbage collector, which in turn can finalize unused tables.
Finalization of tables has therefore been delayed by using an action.
Plus one trivial Optimization: empty and NULL VARCHAR strings reuse a common string object.
The BlackBox version for testing:
http://blackboxframework.org/unstable/i ... b1.515.zip
The suggested differences:
http://redmine.blackboxframework.org/pr ... ae881451b2