- Squash the chains of consecutive spaces between compilation
flags to make the build log more readable
- databases/ejdb: pull upstream patch to synchronize with the
new IOWOW struct naming
Reported by: portscout
lfcbase:
- Warning elimination in several code modules.
-Wall should print no warnings anymore (with clang)
cego:
- Added patch for CegoJoinObject for correct and complete decoding.
This is needed for database recovery procedure if nested join select
occurs in update statement, e.g.
update t1 set b1 = ( select max(b2) from t2 inner join t3 on t2.a2 = t3.a3 );
- Warning elimination for several code modules.
In CegoContentObject encoding and decoding method,
the obsolete key flag in the schema information was removed.
This leads to a incompatibel datastructure and requires tableset
export/import for an uplift ot this version
- To toChain method of CegoTableObject, CegoJoinObject and
CegoAliasObject has been improved to treat undefined tabSetId
argument ( defTabSetId = 0 ).
lfcbase:
- Added patch in File::hasData to check return code of pool library call
- Added fix in basecheck ReplaceTest to return valid results
cego:
- For CegoClient and CegoAdmin changed argument evaluation to handle
pipe input data in a better way.
Pipe mode is just used, if no batch or command mode ist setup and
if data is available at stdin.
- This should also work for FreeBSD, when cgclt or cgadm is used
via cronjob. It has been observed, that if a program is called by
cron, poll returns data available at stdin also if there is no data
available.
- In CegoAdminThread, for tableset and table import procedure added
switch to next backup branch.
This is required, since during import, logging is disabled.
So after import, a new backup is needed.
The previous upstream has been unfetchable for quite a while.
There are a number of forks, of which https://github.com/GnoTime/qof
seems to be the most active. It is also the same GH account as
is used by deskutils/gnotime, which is our only in-tree consumer.
Take MAINTAINERship and undeprecate.
MFH: 2025Q4
Active Record connects classes to relational database tables to establish an
almost zero-configuration persistence layer for applications. The library
provides a base class that, when subclassed, sets up a mapping between the new
class and an existing table in the database. In the context of an application,
these classes are commonly referred to as models. Models can also be connected
to other models; this is done by defining associations.
Active Record relies heavily on naming in that it uses class and association
names to establish mappings between respective database tables and foreign key
columns. Although these mappings can be defined explicitly, it's recommended to
follow naming conventions, especially when getting started with the library.
Active Model provides a known set of interfaces for usage in model classes. They
allow for Action Pack helpers to interact with non-Active Record models, for
example. Active Model also helps with building custom ORMs for use outside of
the Rails framework.
Active Model provides a default module that implements the basic API required to
integrate with Action Pack out of the box: ActiveModel::API.
This reverts commit b7fb45fcb4cfb4a9e0edb7d4e67edb7f11e104f7.
This was already updated to 3.8.0 - applying the patch a second time puts it back to 3.7.3.
Reported by: Martin Birgmeier <d8zNeCFG@aon.at> and portmgr@
The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 18.1, 17.7, 16.11, 15.15,
14.20, and 13.23. This release fixes 2 security vulnerabilities and over
50 bugs reported over the last several months.
This is the final release of PostgreSQL 13. PostgreSQL 13 is now
end-of-life and will no longer receive security and bug fixes.
Release notes: https://www.postgresql.org/about/news/postgresql-181-177-1611-1515-1420-and-1323-released-3171/
