git: 4c4ce8d3853f - main - databases/cego: upgrade 2.47.16 -> 2.47.22

From: Kurt Jaeger <pi_at_FreeBSD.org>
Date: Sun, 20 Feb 2022 13:05:16 UTC
The branch main has been updated by pi:

URL: https://cgit.FreeBSD.org/ports/commit/?id=4c4ce8d3853f42823802c297c74a06d453bc1639

commit 4c4ce8d3853f42823802c297c74a06d453bc1639
Author:     Björn Lemke <lemke@lemke-it.com>
AuthorDate: 2022-02-20 13:03:57 +0000
Commit:     Kurt Jaeger <pi@FreeBSD.org>
CommitDate: 2022-02-20 13:03:57 +0000

    databases/cego: upgrade 2.47.16 -> 2.47.22
    
    - Fix in CegoFunction::clone, also if _exprList is empty, the function
      must treated and cloned completely including table manager reference.
      Otherwise, for user defined function with no arguments which are used
      in views will throw an exception
    - Change in CegoJDBCInfo for table list retrievel. This JDBC meta
      information command is not split to tab and vie for dedicated
      retrievel of table and view objects
    - More work has been done regarding clean shutdown of the
      database / tableset stop while busy db sessions still exist.
      For this, CegoDistCursr desctructor method has been stabilized,
      so no exception is thrown. Otherwise, double memory freeing of
      cursor resources might occur which results in a crash
    - In CegoTableManager::stopTableset, relocated the setTableSetRunState
      method above and added a sleep of DBM_LOCKDELAY. This gives hanging
      db threads a chance, to terminate save
    - Changed CegoDatabaseManager::useObject method to take pointer to
      CegoTableManager as an argument instead of threadId. The tablemanager
      is used to support thread termination in case of lock delays
    - Fix in CegoTableManager::createBTree to catch exclusicve useObject
      timeout before committing btree. In this case, the already created
      btree object should be deleted. Fix added in CegoClient to active
      abort interrupt also during tuple fetch
    - Added function getcount to retrieve current counter value for
      a specific counter
    - Fix in CegoLogManager::stopLog, the log handle must NOT be deleted,
      otherwise, a subsequent startLog and logAction method will result
      in a dump. This effect has been observed while importing a single
      table ( via xml import ) which failed, if the table already exists.
      In this case, no checkpoint is written and log handle i no more
      valid. A subsequent modifying db request then results in a core
      dump.
---
 databases/cego/Makefile | 2 +-
 databases/cego/distinfo | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/databases/cego/Makefile b/databases/cego/Makefile
index 18c2cc2f2fa0..e9a2d78afe52 100644
--- a/databases/cego/Makefile
+++ b/databases/cego/Makefile
@@ -1,5 +1,5 @@
 PORTNAME=	cego
-PORTVERSION=	2.47.16
+PORTVERSION=	2.47.22
 CATEGORIES=	databases
 MASTER_SITES=	http://www.lemke-it.com/
 
diff --git a/databases/cego/distinfo b/databases/cego/distinfo
index dcfe7f98329a..b7a3585c116f 100644
--- a/databases/cego/distinfo
+++ b/databases/cego/distinfo
@@ -1,3 +1,3 @@
-TIMESTAMP = 1642246166
-SHA256 (cego-2.47.16.tar.gz) = 304fbc8c8fb6c240912dc76ff16acee12495d99378428590fb431491616bb741
-SIZE (cego-2.47.16.tar.gz) = 3168774
+TIMESTAMP = 1645292214
+SHA256 (cego-2.47.22.tar.gz) = 726d11813fa0cf7a95ff0b8c4cbfd56f7cca804398f5f7c8a66d84a068b183cd
+SIZE (cego-2.47.22.tar.gz) = 3171302