Cego Änderungsprotokoll
In the following, change log entries for the managed software packages is shown
Last 10 30 100 1000 10000 entries
| Category | Date | Version | Log |
|---|---|---|---|
| cego | 01.04.2024 | 2.48.48 | Version released |
| cego | 30.03.2024 | 2.48.48 | Fix in CegoAdmScreen::TableSet::TableSet constructor, SysUsage field added to indicate correct usage for system, temp and app files |
| cego | 29.03.2024 | 2.48.47 | Version released |
| cego | 29.03.2024 | 2.48.47 | Sample code for transaction effect :
---
drop if exists table t1; create table t1 (a int, b string(10)); start transaction; insert into t1 values ( 1, 'XXX'); insert into t1 values ( 1, 'XXX'); insert into t1 values ( 1, 'XXX'); -- here a double delete may occur delete from t1; commit; insert into t1 values ( 1, 'XXX'); select * from t1; |
| cego | 29.03.2024 | 2.48.47 | Patch added for transaction handling in CegoTransactionManager::doCommit and CegoTableManager::deleteDataTableEntry. Just for tuple state COMMITTED, a rollback entry must be created, otherwise double tuple delete may occur. For tuple state INSERTED, tuple state is just set to OBSOLETE, for tuple state OBSOLETE and DELETED, nothing has to be done. In CegoTableManager::doCommit, tuple state just has to be set to COMMITTED in case of INSERTED tuples |
| cego | 26.03.2024 | 2.48.46 | Version released |
| cego | 26.03.2024 | 2.48.46 | Elimination of a cout in CegoQueryCache::QueryCacheEntry::cleanCache |
| cegojdbc | 17.03.2024 | 1.10.6 | Version released |
| cegojdbc | 17.03.2024 | 1.10.6 | Elimination of several warnings in code caused by legacy constructs |
| cego | 17.03.2024 | 2.48.45 | Version released |