× News Cego SysMT Croom Web Statistics Impressum
SysMT Logo
Change Log

In the following, change log entries for the managed software packages are shown

Last 10 30 100 1000 10000 entries

Category Date Version Log
cego 19.04.2024 2.48.49 In CegoCaseCond, added getPlanList method to retrieve execution plan for nested selects. The planlist then is catched in CegoFactor::getPlanList
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
cego 17.03.2024 2.48.45 Added patches for return on update handling to treat value handling in return list. The order in the return list must be stricter, otherwise field evaluation via FLA caching in CegoFactor fails.
Furthermore, returnList has been localized ( new method CegoQueryHelper::localizeFL ) to ensure correct values after update cursor ist closed.
cego 15.03.2024 2.48.44 Version released
cego 15.03.2024 2.48.44 Patch added in CegoXPorter to improve exception handling for invalid export file names
cego 06.03.2024 2.48.43 Version released
cego 06.03.2024 2.48.43 Added patch in CegoSelect::evalSchema to treat null values for union all, added patch in CegoFunction::clone to treat counterId value
cegojdbc 28.02.2024 1.10.5 Version released
cegojdbc 28.02.2024 1.10.5 Added patch for CegoStatement.executeQuery, result set handling was not done correctly, if result sets are retrieve via getResultSet statement method
cego 13.02.2024 2.48.42 Version released
cego 13.02.2024 2.48.42 In CegoDistCursor::nextTuple, added query aborted check. This is needed to abort long running inner and outer join selects
cego 10.02.2024 2.48.41 Version released
cego 10.02.2024 2.48.41 Patch added in CegoProcedure::cleanup to set pMasterBlock to zero. In some cases, the setup master block lead to usage leaks for user function calls. See check110.sql as a sample to cause this problem.
cego 03.02.2024 2.48.40 Version released
cego 03.02.2024 2.48.40 Small patch on CegoDistManager::startTableSet, improvement for exception message added
cego 27.01.2024 2.48.39 Version released
cego 27.01.2024 2.48.39 Patch added in CegoAdminThread::srvParameterInfo to list current QUEUEDELAY value and configured scandal formats ( SCANDATETIMEFORMAT )
cego 08.01.2024 2.48.38 Version released
cego 08.01.2024 2.48.38 Patch added in CegoQueryHelper::evalBetween The comparison ( f2 <= f1 && f1 <= f3 ) has changed to ( f1 >= f2 && f1 <= f3 ) This forces a type cast to f1 datatype in case mismatched datatypes. This might be useful for queries like select a from v1 where a between '30.11.2023' and '31.12.2023'; where a cast should be done to date time value ( instead of string )
cego 19.12.2023 2.48.37 Version released
cego 19.12.2023 2.48.37 Patch added in CegoQueryHelper::encodeFL and CegoQueryHelper::decodeFL. Die dim field value was still not treated. This might lead to wrong fixed values for update operations during crash recovery operation