databases/cego: 2.38.19 -> 2.38.20

• For heavy update operations on tables with btrees using embedding transactions, duplicate btree errors may occur. This is caused by not checking corresponding tuple states. To solve this problem, the following fixes have been done : o Fix in CegoTableManager::checkBTreeIntegrity : The tuple state for found entries has to be checked if state = COMMITTED o Fix in CegoBTreeNode:checkForAffected ( was checkForDeleted before ) : The tuple state has already checked for state INSERTED if tid != dataTid

Submitted by: Bjoern Lemke <lemke@lemke-it.com>