databases/pgaccess: revert removal
This reverts commit c7292eb0fa666fb738328675d0d35e6bbcdf323e per
maintainer request. Re-do distinfo with timestamp so it can be
committed.
PR: 277665
databases/mysql84-{server|client}: add new Ports
Welcome MySQL 8.4
What is new in MySQL8.4 since MySQL 8.0:
https://dev.mysql.com/doc/refman/8.4/en/mysql-nutshell.html
HINT: MySQL8.2+ supports only 64-bit platforms!!!
special thanks for the majority of the work on this port: samm aka Alex
S.
databases/foundationdb*: split, update to 7.1.59 & 7.3.41
Update FoundationDB to both main supported versions, and also split
between server and client builds for convenience.
PR: 277262
Reviewed by: dch
Sponsored by: SkunkWerks, GmbH
databases/pgsphere: Remove expired port
2024-04-30 databases/pgsphere: The repository has been archived by the owner on
2023-08-09 and is inactive for almost 4.5 years
databases/R-cran-dbplyr: New port: 'dplyr' Back End for Databases
- Submitter becomes maintainer
A 'dplyr' back end for databases that allows you to work with remote database
tables as if they are in-memory data frames. Basic features works with any
database that has a 'DBI' back end; more advanced features require 'SQL'
translation to be provided by the package author.
WWW: https://dbplyr.tidyverse.org/
Differential Revision: https://reviews.freebsd.org/D43735
databases/R-cran-dtplyr: New port: Data Table Back-End for 'dplyr'
- Submitter becomes maintainer
Provides a data.table backend for 'dplyr'. The goal of 'dtplyr' is to allow you
to write 'dplyr' code that is automatically translated to the equivalent, but
usually much faster, data.table code.
WWW: https://dtplyr.tidyverse.org/
Differential Revision: https://reviews.freebsd.org/D43735
databases/percona-orchestrator: new port!
Orchestrator is a replication topology manager for MySQL.
Features include:
* The topology and status of the replication tree is automatically detected
and monitored.
* Either a GUI, CLI or API can be used to check the status and perform
operations.
* Supports automatic failover of the master, and the replication tree can
be fixed when servers in the tree fail - either manually or automatically.
* It is not dependent on any specific version or flavor of MySQL (MySQL,
Percona Server, MariaDB or even MaxScale binlog servers).
* Orchestrator supports many different types of topologies, from a single
master -> slave to complex multi-layered replication trees consisting of
hundreds of servers.
* Orchestrator can make topology changes and will do so based on the state
at that moment; it does not require a configuration to be defined with what
corresponds to the database topology.
* The GUI is not only there to report the status - one of the cooler things
you can do is change replication just by doing a drag and drop in the web
interface (of course you can do this and much more through the CLI and API
as well).
databases/proxysql: New port!
ProxySQL is a high performance, high availability, protocol aware proxy for
MySQL and forks (like Percona Server and MariaDB).
With its ability to intelligently route queries, balance loads, and provide
failover handling, ProxySQL empowers organizations to harness the full
potential of their database infrastructure. Whether grappling with
scalability challenges, striving to enhance performance, or seeking to
ensure high availability, ProxySQL emerges as a versatile ally, capable of
addressing diverse needs across various database environments.
WWW: https://www.proxysql.com/
databases/pgpool-II-45: New port
pgpool is a connection pool server for PostgreSQL. pgpool runs between
PostgreSQL's clients(front ends) and servers(back ends). A PostgreSQL
client can connect to pgpool as if it were a standard PostgreSQL server.
pgpool caches the connection to PostgreSQL server to reduce the overhead
to establish the connection to it.
This is the 4.5.X series of the port.
WWW: https://pgpool.net
databases/xtrabackup80: renamed from databases/xtrabackup8 and updated
The port databases/xtrabackup8 upgraded to version 8.0.35-30
and renamed to databases/xtrabackup80 in preparation for upcoming
incompatible branch databases/xtrabackup81, to avoid confusion.
Drop unused dependency on libncurses.
The update based on maintainer's submittion.
PR: 277088
Tested by: Eugene M. Zheganin (maintainer)
Approved by: Eugene M. Zheganin (maintainer)
databases/pg_vector: Rename to match upstream and fix license
Also split DISTVERSION into PORTVERSION and DISTVERSIONPREFIX
PR: 276846
Reported by: Andrew Kane <andrew@ankane.org>
databases/qt5-sqldrivers-ibase: Remove expired port
2024-01-21 databases/qt5-sqldrivers-ibase: No fix with the oldest Firebird and
BROKEN around 1 year
databases/adminerevo: New port
AdminerEvo (fork of Adminer) is a full-featured database management tool
written in PHP. Conversely to phpMyAdmin, it consists of a single file
ready to deploy to the target server.
WWW: https://adminerevo.org
PR: 274188
add databases/mysql81-server and databases/mysql81-client
Welcome MySQL81 to the Port Tree
Special thanks for help: fluffy, both
Sponsored by: Netzkommune GmbH
databases/rubygem-google-cloud-firestore-v1: Add
rubygem-google-cloud-firestore-v1 0.10.0
Ruby Client for the Cloud Firestore V1 API
Accesses the NoSQL document database built for automatic scaling, high
performance, and ease of application development.
Cloud Firestore is a NoSQL document database built for automatic scaling, high
performance, and ease of application development.
databases/rubygem-google-cloud-firestore: Add rubygem-google-cloud-firestore
2.13.1
Cloud Firestore is a NoSQL document database built for automatic scaling, high
performance, and ease of application development. While the Cloud Firestore
interface has many of the same features as traditional databases, as a NoSQL
database it differs from them in the way it describes relationships between data
objects.
databases/rubygem-google-cloud-datastore-v1: Add
rubygem-google-cloud-datastore-v1 0.14.0
Ruby Client for the Firestore in Datastore mode V1 API
Accesses the schemaless NoSQL database to provide fully managed, robust,
scalable storage for your application.
Firestore in Datastore mode is a NoSQL document database built for automatic
scaling, high performance, and ease of application development.
databases/rubygem-google-cloud-datastore: Add rubygem-google-cloud-datastore
2.8.0
google-cloud-datastore is the official library for Google Cloud Datastore.
Google Cloud Datastore is a fully managed, schemaless database for storing
non-relational data. Cloud Datastore automatically scales with your users and
supports ACID transactions, high availability of reads and writes, strong
consistency for reads and ancestor queries, and eventual consistency for all
other queries.
lang/fpc-*: Merge all units to lang/fpc
- Merge all fpc-* units to lang/fpc. It gives us a better way to maintain fpc
and lazarus ports.
- Update Mk/fpc.mk for reflects new changes
- Update Mk/lazarus.mk for reflects new changes
- Now we can defined WANT_FPC_DEVEL AND WANT_LAZARUS_DEVEL for use devel version
of fpc or lazarus for build apps based on fpc/lazarus
- Add entries to MOVED
- Bump PORTREVISON of affected ports
- Some other minor modifications
databases/rubygem-activerecord71: Add rubygem-activerecord71 7.1.1
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.
databases/rubygem-activemodel71: Add rubygem-activemodel71 7.1.1
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.
databases/keydb: New port!
KeyDB is a high performance fork of Redis with a focus on multithreading,
memory efficiency, and high throughput. In addition to performance
improvements, KeyDB offers features such as Active Replication, FLASH
Storage and Subkey Expires. KeyDB has a MVCC architecture that allows you
to execute queries such as KEYS and SCAN without blocking the database and
degrading performance.
KeyDB maintains full compatibility with the Redis protocol, modules, and
scripts. This includes the atomicity guarantees for scripts and transactions.
Because KeyDB keeps in sync with Redis development KeyDB is a superset of
Redis functionality, making KeyDB a drop in replacement for existing Redis
deployments.
On the same hardware KeyDB can achieve significantly higher throughput than
Redis. Active-Replication simplifies hot-spare failover allowing you to
easily distribute writes over replicas and use simple TCP based load
balancing/failover. KeyDB's higher performance allows you to do more on less
hardware which reduces operation costs and complexity.
WWW: https://docs.keydb.dev/
databases/py-snowddl: new port
SnowDDL is a declarative-style tool for object management automation in
Snowflake.
It is not intended to replace other tools entirely, but to provide an
alternative approach focused on practical data engineering challenges.
You may find SnowDDL useful if:
- complexity of object schema grows exponentially, and it becomes hard to manage
- your organization maintains multiple Snowflake accounts (dev, stage, prod)
- your organization has multiple developers sharing the same Snowflake account
and suffering from conflicts
- it is necessary to generate some part of configuration dynamically using
Python
PR: 274586
Author: Pat Maddox <pat@patmaddox.com>
databases/py-schemachange: new port
schemachange is a simple python based tool to manage all of your Snowflake
objects. It follows an Imperative-style approach to Database Change Management
(DCM) and was inspired by the Flyway database migration tool. When combined with
a version control system and a CI/CD tool, database changes can be approved and
deployed through a pipeline using modern software delivery practices. As such
schemachange plays a critical role in enabling Database (or Data) DevOps.
PR: 274585
Author: Pat Maddox <pat@patmaddox.com>
databases/py-dbt-duckdb: new port
dbt-duckdb
DuckDB is an embedded database, similar to SQLite, but designed for OLAP-style
analytics. It is crazy fast and allows you to read and write data stored in CSV,
JSON, and Parquet files directly, without requiring you to load them into the
database first.
dbt is the best way to manage a collection of data transformations written in
SQL or Python for analytics and data science. dbt-duckdb is the project that
ties DuckDB and dbt together, allowing you to create a Modern Data Stack In A
Box or a simple and powerful data lakehouse with Python.
PR: 274584
Author: Pat Maddox <pat@patmaddox.com>
databases/py-dbt-snowflake: new port
The dbt-snowflake package contains all of the code enabling dbt to work with
Snowflake.
PR: 274583
Author: Pat Maddox <pat@patmaddox.com>
databases/py-dbt-core: new port
dbt enables data analysts and engineers to transform their data using the same
practices that software engineers use to build applications.
Analysts using dbt can transform their data by simply writing select statements,
while dbt handles turning these statements into tables and views in a data
warehouse.
These select statements, or "models", form a dbt project. Models frequently
build on top of one another - dbt makes it easy to manage relationships between
models, and visualize these relationships, as well as assure the quality of your
transformations through testing.
PR: 274582
Author: Pat Maddox <pat@patmaddox.com>
databases/py-snowflake-connector-python: new port
The Snowflake Connector for Python conforms to the Python DB API 2.0
specification.
The Snowflake Connector for Python provides an interface for developing Python
applications that can connect to Snowflake and perform all standard
operations. It provides a programming alternative to developing applications in
Java or C/C++ using the Snowflake JDBC or ODBC drivers.
The connector has no dependencies on JDBC or ODBC. It can be installed using pip
on Linux, Mac OSX, and Windows platforms where Python 3.8.0 (or higher) is
installed.
PR: 274576
Author: Pat Maddox <pat@patmaddox.com>
databases/py-dbt-semantic-interfaces: new port
dbt-semantic-interfaces contains the shared semantic classes, default
validation, and tests designed to be used by both the dbt-core and MetricFlow
projects. By centralizing these shared resources, we aim to maintain consistency
and reduce code duplication across both projects.
Features:
- Protocols for shared semantic classes: Define the interfaces and common
attributes that must be implemented by the objects in both projects.
- Validation: Ensure that the objects comply with the expected structure and
constraints.
- Tests: Ensure that the objects' behavior is consistent and correct across both
projects.
PR: 274581
Author: Pat Maddox <pat@patmaddox.com>
databases/trilogy: Add trilogy 2.6.0
Trilogy is a client library for MySQL-compatible database servers, designed for
performance, flexibility, and ease of embedding.
It's currently in production use on github.com.
Features:
- Supports the most frequently used parts of the text protocol
- Handshake
- Password authentication
- Query, ping, and quit commands
- Support prepared statements (binary protocol)
- Low-level protocol API completely decoupled from IO
- Non-blocking client API wrapping the protocol API
- Blocking client API wrapping the non-blocking API
- No dependencies outside of POSIX, the C standard library & OpenSSL
- Minimal dynamic allocation
- MIT licensed
databases/rubygem-activerecord-trilogy-adapter: Add
rubygem-activerecord-trilogy-adapter 3.1.2
Trilogy Adapter is a Ruby on Rails Active Record database adapter for Trilogy, a
client library for MySQL-compatible database servers, designed for performance,
flexibility, and ease of embedding.
databases/py-pyarrow: Add py-pyarrow 13.0.0
Python library for Apache Arrow provides a Python API for functionality provided
by the Arrow C++ libraries, along with tools for Arrow integration and
interoperability with pandas, NumPy, and other software in the Python ecosystem.
databases/rubygem-red-plasma: Remove obsoleted port
red-plasma is deprecated since 10.0.0. red-plasma will not be released from
Apache Arrow 12.0.0 or so.
databases/mysql-connector-j: Renamed and updated to 8.1.0
Starting on 8.0.31, upstream has renamed the port to mysql-connector-j
and the groupId and artifactId has changed to comply with proper naming
guidelines. Please read the changelog for more details.
Changes: https://dev.mysql.com/doc/relnotes/connector-j/8.1/en/news-8-1-0.html
databases/pgpool-II-44: New port
pgpool is a connection pool server for PostgreSQL. pgpool runs between
PostgreSQL's clients(front ends) and servers(back ends). A PostgreSQL
client can connect to pgpool as if it were a standard PostgreSQL server.
pgpool caches the connection to PostgreSQL server to reduce the overhead
to establish the connection to it.
databases/futuresql: new port -- A non-blocking database framework for Qt.
FutureSQL was in part inspired by Diesel, and provides a higher level of
abstraction than QtSql. Its features include non-blocking database access by
default, relatively boilderplate-free queries, automatic database migrations
and simple mapping to objects.
In order to make FutureSQL's use of templates less confusing, FutureSQL uses
C++20 concepts, and requires a C++20 compiler.
Warning: The API is not finalized yet.
databases/rubygem-attr_json: Add rubygem-attr_json 2.1.0
ActiveRecord attributes stored serialized in a json column, super smooth.
Typed and cast like Active Record. Supporting nested models, dirty tracking,
some querying (with postgres jsonb contains), and working smoothy with form
builders.
Use your database as a typed object store via ActiveRecord, in the same models
right next to ordinary ActiveRecord column-backed attributes and associations.
Your json-serialized attr_json attributes use as much of the existing
ActiveRecord architecture as we can.
databases/postgresql-idn New port
At a fundamental level, this extension grants access to a number of
functions provided by the libidn and libidn2 libraries. Not all of the
functions provided by these libraries are exposed.
Whenever possible, the code will transform the encoding of the data in
the database to UTF-8 before further processing.
WWW: https://github.com/dyninc/postgresql-idn
Sponsored by: Bounce Commerce
databases/caterva: Remove expired port
2023-06-30 databases/caterva: Use archivers/c-blosc2 instead. All the features
of Caterva have been included in the C-Blosc2 NDim object
databases/py-caterva: Remove expired port
2023-06-30 databases/py-caterva: Use archivers/py-blosc2 instead. All the
features of Python-Caterva have been included in the Python-Blosc2 NDArray
object
Approved by: portmgr (blanket)