(well) on FreeBSD. Then the port used en embedded copy of QScintilla.
Switch to using the system QScintilla.
This change is triggered by CMake 3.11, which tried to build the embedded
QScintilla slightly differently. That fails because there are header
files declaring enum { SCI_CANREDO = 2016 } *and also* header files
that #define SCI_CANREDO 2016; the include order is very fragile.
Also reported upstream.
Reviewed by: lbartoletti_tuxfamily (maintainer)
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D14930
- Patch in CegoClient to catch format exceptions like
"Invalid datetime string <0> for format <%d.%m.%Y %H:%M:%S>"
This may happen, if on server side bad union selects are defined like
create view v1 as
select a as a, b as b from t1
union all
select a as a, 0 as b from t2;
where b is a datetime data type. In this case, invalid formatted
strings occur on the client side, which are catched now.
- Patch in CegoDatabaseManager::useObject to support lock
delay values > 1 sec. The DBM_LOCKDELAY value in CegoDefs has now
increased to 2500 msec. In some cases for heavy updates
( e.g. clob updates ) this might be useful to avoid ugly exclusive
lock delay messages in database log file
- Fix in CegoTableManager::updateTuple. If the update fails ( this
might happen, if another transaction actually updates the corresponding
tuple ), any allocated lob values are freed now. Otherwise the
data pages for the lob values were allocated with no more references.
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
Regarding to the changes to rc.subr(8) it is no longer necessary to
define a resource limiting logic in service scripts.
limits(1) is now run by default and its configuration is handled
via the "${name}_limits" variable.
This however causes collision of variable names and also is not
compatible with the old mechanism.
This fixes the rc-script of mysql80 for the bases with both
old and new mechanism.
(This is port of the r466505 [and r466506])
PR: 227231
Submitted by: 0mp
Reported by: 0mp
Sponsored by: Netzkommune GmbH
Regarding to the changes to rc.subr(8) it is no longer necessary to
define a resource limiting logic in service scripts.
limits(1) is now run by default and its configuration is handled
via the "${name}_limits" variable.
This however causes collision of variable names and also is not
compatible with the old mechanism.
This fixes the rc-script of mysql57 for the bases with both
old and new mechanism.
(This is port of the r466505 [and r466506])
PR: 227230
Submitted by: 0mp
Reported by: 0mp
Differential Revision: Netzkommune GmbH
Regarding to the changes to rc.subr(8) it is no longer necessary to
define a resource limiting logic in service scripts.
limits(1) is now run by default and its configuration is handled
via the "${name}_limits" variable.
This however causes collision of variable names and also is not
compatible with the old mechanism.
This fixes the rc-script of mysql56 for the bases with both
old and new mechanism.
PR: 227229
Submitted by: 0mp
Reported by: 0mp
Sponsored by: Netzkommune GmbH
Enabling DTRACE option causes build failure.
It appears this option never really worked on FreeBSD.
PR: 217097
Submitted by: sunpoet (myself)
Approved by: Mikhail Tsatsenko <m.tsatsenko@gmail.com> (maintainer)
Thanks to: John Hein <z7dr6ut7gs@snkmail.com> (for analysis and testing)
src/libedataserver/e-alphabet-index-private.cpp:79:2: error: unknown type name 'UnicodeString'; did you mean 'icu::UnicodeString'?
UnicodeString string;
^~~~~~~~~~~~~
icu::UnicodeString
/usr/local/include/unicode/unistr.h:286:20: note: 'icu::UnicodeString' declared here
class U_COMMON_API UnicodeString : public Replaceable
^
src/libedataserver/e-alphabet-index-private.cpp:132:3: error: unknown type name 'UnicodeString'; did you mean 'icu::UnicodeString'?
UnicodeString ustring;
^~~~~~~~~~~~~
icu::UnicodeString
/usr/local/include/unicode/unistr.h:286:20: note: 'icu::UnicodeString' declared here
class U_COMMON_API UnicodeString : public Replaceable
^
https://ssl.icu-project.org/trac/changeset/40705
PR: 227042
Reported by: antoine (via exp-run)
- Improvements for log handling, the logIt method was moved from
CegoTableManager to CegoBufferPool. This allows a more adequate
locking of the logging actions. For this the tsLock array has been
removed from CegoTableManager and lmLock array has been set up in
CegoBufferPool. Since checkpoint writing occurs in CegoBufferPool
( which is also relevant for loging operations ), the logging method
is now part of CegoBufferPool.
- The logAction method in CegoLogManager has also been improved in
a way, that a log buffer is not allocated for each logging operation
anymore. Instead, a logBuf array has been defined for all tablesets
and the logBuf is reallocated, if the current logging record exceeds
the log buffer.
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
LMDB 0.9.22 Release (2018-03-22)
Fix MDB_DUPSORT alignment bug (ITS#8819)
Fix regression with new db from 0.9.19 (ITS#8760)
Fix liblmdb to build on Solaris (ITS#8612)
Fix delete behavior with DUPSORT DB (ITS#8622)
Fix mdb_cursor_get/mdb_cursor_del behavior (ITS#8722)
PR: 227103
Submitted by: gahr
Approved by: delphij (maintainer)
For the qt5-* ports bsd.qt.mk sets EXTRACT_AFTER_ARGS, and
thereby does not get the normal default value of
--no-same-owner --no-same-permissions
passed when extracting. This lead to for example header files
being installed (i.e. copied), with permissions group write
permissions.
Manually append that to the bsd.qt.mk shenanigans (also do the
same in www/qt5-webchannel, which opts out of the bsd.qt.mk value)
PR: 227027
Reported by: grarpamp@gmail.com
- Added fixes for recovery procedure in CegoTableManager. Now the
LSN is allocated at the beginning of critical operation to avoid
double operations in case of a forced checkpoint. For this the
CegoLogManager::nextLSN method has been introduced. Now it is no
more ensured that the log is written with increasing LSN, so some
logical parts of the recovery procedure in CegoRecoveryManager has
been changed.
- In CegoBufferPool, the writeCheckPoint method still returned int
value. This has been changed to unsigned long long
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
