| Änderungsprotokolle |
|---|
Im folgenden sind die letzten Änderungen der verschiedenen Softwarepakete aufgeführt.
Letze 10 30 100 1000 10000 Einträge
| Kategorie | Datum | Version | Eintrag |
|---|---|---|---|
| cego | 15.03.2026 | 2.54.18 | Version released |
| cego | 15.03.2026 | 2.54.18 | Improved exception handling for NETMNG_MAXSERCHAIN validation in CegoNet and CegoClient. In case of a validation, the connection on client side is closed in a controlled way with message "Fatal protocol error". Since there is no way to get more information from server side, this is ok.
On server side, in case of MAXSERCHAIN validation, the connection must be closed immediately ( also for security reasons ), since the serial protocol can not be reset or recovered In CegoDefs, NETMNG_MAXSERCHAIN has been increased to 4MB |
| cego | 14.03.2026 | 2.54.17 | Version released |
| cego | 14.03.2026 | 2.54.17 | In CegoDefs.h, introduced NETMNG_MAXSERCHAIN which defines the maxium length of a serial protocol message ( see CegoSerial.h ) For database configuration, which are using CLOBS, this value should bet setup large enough ( standard now 1MB ) |
| cego | 13.03.2026 | 2.54.16 | Version released |
| cego | 13.03.2026 | 2.54.16 | Fix for include added in CegoXMLSpace.h ( CegoAdminHandler.h was included with brackets, which leads to compile problem for using packages, should be included with quotes ) |
| cego | 05.03.2026 | 2.54.15 | Version released |
| cego | 05.03.2026 | 2.54.15 | In CegoClient, query abort via Cntrl-C was broken. This was caused by the pager mode expansion, which requires a special signal handling setup. For interactive mode, setup method was introduced to setup signals SIGINT and SIGPIPE |
| cego | 05.03.2026 | 2.54.15 | In CegoTableManager::checkBTreeIntegrity, improved message for duplicate btree values ( with validating btree value ) |
| cego | 02.03.2026 | 2.54.14 | Version released |
| cego | 01.03.2026 | 2.54.14 | Completed verify locks command with missing pool, querycache, tablecache, db and xml locks |
| cego | 01.03.2026 | 2.54.13 | Version released |
| cego | 01.03.2026 | 2.54.13 | In CegoLockHandler, added check for unlock methods to check for lockId == 0. This ensures to avoid unlock operations of undefined lockIds which can impact semaId=0 ( first record lock ). It has been observed, that in deadlock situations, this might lead to locking leaks for RECLOCK-0 |
| cego | 01.03.2026 | 2.54.13 | In CegoTableManager::checkBTreeIntegrity added support for allowDuplicateNull feature ( multiple null values in unique btree ) |
| cego | 28.02.2026 | 2.54.12 | Version released |
| cego | 27.02.2026 | 2.54.12 | Fix added in CegoQueryHelper::maxFieldSize. The returned size must be at least MAX_NULL_LEN, otherwise format errors occur ( string(1) field with null values ) |
| cego | 27.02.2026 | 2.54.12 | Added admin command "verify locks" to perform a test aquire of all lock manager locks read and write |
| cego | 27.02.2026 | 2.54.11 | Version released |
| cego | 27.02.2026 | 2.54.11 | Small exception improvement added for CegoFactor::evalFieldValue for query case |
| cegojdbc | 25.02.2026 | 1.16.1 | removed logback.xml to avoid logging side effects |
| cego | 25.02.2026 | 2.54.10 | Version released |
| cego | 24.02.2026 | 2.54.10 | Rework of tableset verification procedure. Using plain output format now, more details added and bugs removed |
| cego | 24.02.2026 | 2.54.9 | Version released |
| cego | 24.02.2026 | 2.54.9 | Added patch in CegoBtreeNode::verifyLeafFull. Before decoding values via CegoQueryHelper::decodeFVL, the btree schema has to be sorted in terms of field id. Otherwise, decoding might be not complete in case of non-ascending btree attributes. |
| cego | 19.02.2026 | 2.54.8 | Version released |
| cego | 19.02.2026 | 2.54.8 | Fix added in CegoAdminThread::srvVerifyTableSet for view loop iterator Cleanup distributed legacy stuff in CegoAdminHandler::syncWithInfo |
| cego | 14.02.2026 | 2.54.7 | Version released |
| cego | 13.02.2026 | 2.54.7 | Added patch in CegoAction::execProcCall and CegoAction::execFuncCall, in case of an exception, for the procedure instance, a cleanup should be called, otherwise the lock will not be released fail002 has been added for this scenario |
| cego | 08.02.2026 | 2.54.6 | Version released |
| lfcbase | 08.02.2026 | 1.23.3 | Version released |