aboutsummaryrefslogtreecommitdiff
path: root/devel/rubygem-spring-watcher-listen/files/patch-gemspec
diff options
context:
space:
mode:
authorBjörn Lemke <lemke@lemke-it.com>2022-02-20 13:03:57 +0000
committerKurt Jaeger <pi@FreeBSD.org>2022-02-20 13:03:57 +0000
commit4c4ce8d3853f42823802c297c74a06d453bc1639 (patch)
tree757834dded967d4b4e5eba36ef0a9481bc797bda /devel/rubygem-spring-watcher-listen/files/patch-gemspec
parentce68ff693814a9e4a788e09b66d3d08118a0a37d (diff)
downloadports-4c4ce8d3853f42823802c297c74a06d453bc1639.tar.gz
ports-4c4ce8d3853f42823802c297c74a06d453bc1639.zip
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.
Diffstat (limited to 'devel/rubygem-spring-watcher-listen/files/patch-gemspec')
0 files changed, 0 insertions, 0 deletions