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.
pg_incremental is a simple extension that helps you do fast, reliable,
incremental batch processing in PostgreSQL.
With pg_incremental, you define a pipeline with a parameterized query. The
pipeline is executed for all existing data when created, and then periodically
executed. If there is new data, the query is executed with parameter values that
correspond to the new data. Depending on the type of pipeline, the parameters
could reflect a new range of sequence values, a new time range, or a new file.
Sponsored by: P. Variablis GmbH
CyMySQL contains a python MySQL client library.
It is a fork project from PyMySQL.
CyMySQL is accerarated by Cython and supports Python versions 2 and 3.
PoWA (PostgreSQL Workload Analyzer) is a performance tool for PostgreSQL
9.4 and newer allowing to collect, aggregate and purge statistics on
multiple PostgreSQL instances from various Stats Extensions.
PoWA-collector is the daemon that gather performance metrics from remote
PostgreSQL instances (optional) on a dedicated repository server.
pg_cron is a simple cron-based job scheduler for PostgreSQL (10 or higher) that
runs inside the database as an extension. It uses the same syntax as regular
cron, but it allows you to schedule PostgreSQL commands directly from the
database.
Sponsored by: Bounce Commerce
MariaDB Connector/Python enables python programs to access MariaDB
and MySQL databases, using an API which is compliant with the Python
DB API 2.0 (PEP-249). It is written in C and Python and uses MariaDB
Connector/C client library for client server communication.
WWW: https://www.github.com/mariadb-corporation/mariadb-connector-python
PR: 275157
sqloxide wraps rust bindings for sqlparser-rs into a python package using pyO3.
The original goal of this project was to have a very fast, efficient, and
accurate SQL parser I could use for building data lineage graphs across large
code bases (think hundreds of auto-generated .sql files). Most existing sql
parsing approaches for python are either very slow or not accurate (especially
in regards to deeply nested queries, sub-selects and/or table aliases). Looking
to the rust community for support, I found the excellent sqlparser-rs crate
which is quite easy to wrap in python code.
Solid Queue is a DB-based queuing backend for Active Job, designed with
simplicity and performance in mind.
Besides regular job enqueuing and processing, Solid Queue supports delayed jobs,
concurrency controls, recurring jobs, pausing queues, numeric priorities per
job, priorities by queue order, and bulk enqueuing (enqueue_all for Active Job's
perform_all_later).
Solid Queue can be used with SQL databases such as MySQL, PostgreSQL or SQLite,
and it leverages the FOR UPDATE SKIP LOCKED clause, if available, to avoid
blocking and waiting on locks when polling jobs. It relies on Active Job for
retries, discarding, error handling, serialization, or delays, and it's
compatible with Ruby on Rails's multi-threading.
Solid Cache is a database-backed Active Support cache store that let's you keep
a much larger cache than is typically possible with traditional memory-only
Redis or Memcached stores. This is thanks to the speed of modern SSD drives,
which make the access-time penalty of using disk vs RAM insignificant for most
caching purposes. Simply put, you're now usually better off keeping a huge cache
on disk rather than a small cache in memory.
Solid Cable is a database-backed Action Cable adapter that keeps messages in a
table and continously polls for updates. This makes it possible to drop the
common dependency on Redis, if it isn't needed for any other purpose. Despite
polling, the performance of Solid Cable is comparable to Redis in most
situations. And in all circumstances, it makes it easier to deploy Rails when
Redis is no longer a required dependency for Action Cable functionality.
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.
Basic SQLAlchemy driver for DuckDB
Once you've installed this package, you should be able to just use it,
as SQLAlchemy does a python path search
WWW: https://github.com/Mause/duckdb_engine
PR: 278138
Jochen Neumeister
Po-Chuan Hsieh
Rene Ladan
Torsten Zuehlsdorff
Fabien Amelinck
Palle Girgensohn
Colin Percival
Danilo G. Baio
Yuri Victorovich
Loïc Bartoletti
Jesús Daniel Colmenares Oviedo
Pat Maddox