1
0
mirror of https://github.com/MariaDB/server.git synced 2026-10-23 18:49:29 +03:00
Dave Gosselin fc887b9e9f MDEV-41251: Keep the original cache in a copy of an item tree
A copy of an item tree now holds the original Item_cache instead of a
new one, and this includes a row cache, which could not be copied
before.  With t0 holding (1,3), (2,2) and (3,7), the IN subquery over a
split materialized table in the test returned only (1,3), but the same
query without splitting returns (1,3) and (2,2).

The equality pushed into the split table held a copy of the cache of
the IN predicate.  Item_in_optimizer stores a new value into its own
cache for each outer row, yet nothing stored into the copy, so the copy
kept the value of the first row.  The walk that marks the fields of the
pushed equality as dependent no longer enters caches, whose example
belongs to the select of the cache owner.  The debug check of a copy
accepts the shared cache, and the item_cache_clones debug flag now
makes a shallow copy of each new cache.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-08 11:10:36 -04:00
2026-09-04 12:21:02 +02:00
2026-09-04 12:14:15 +02:00
2026-05-22 09:52:05 +02:00
2026-09-15 11:07:31 +02:00
2026-06-15 16:53:03 +02:00
2026-09-04 12:21:02 +02:00
2026-08-12 14:31:53 +03:00
2026-06-15 16:53:03 +02:00
2026-09-04 12:21:02 +02:00
2026-09-04 12:21:02 +02:00
2025-04-29 11:18:00 +10:00
2026-08-20 08:27:14 +02:00
2026-08-03 13:42:39 +02:00
2026-06-15 16:53:03 +02:00
2026-07-30 11:41:55 +02:00
2026-05-22 09:52:05 +02:00
2022-02-03 17:01:31 +01:00
2026-07-30 11:41:55 +02:00
2026-06-15 16:53:03 +02:00
2026-07-28 13:14:38 +02:00
2025-04-29 11:18:00 +10:00
2026-09-04 12:14:15 +02:00
2026-09-04 12:14:15 +02:00
2019-05-11 21:29:06 +03:00
2023-06-05 08:28:06 +10:00
2026-09-09 13:31:16 +02:00

MariaDB Server

MariaDB Server is one of the most widely deployed open source relational databases. It is built by a global community of contributors together with the MariaDB Foundation and MariaDB plc, and it powers workloads from small applications to large-scale production systems.

MariaDB began as a fork of MySQL, led by the original MySQL developers, and it maintains a high degree of MySQL compatibility. It has since grown into a database with its own capabilities, including native vector search, multiple pluggable storage engines, synchronous clustering, and analytical features, while remaining a straightforward migration target for existing MySQL deployments.

Key features

  • Native vector search. A built-in VECTOR data type with approximate nearest-neighbour indexing (HNSW), available since MariaDB 11.8 with no extension required.
  • Pluggable storage engines. InnoDB (default for transactional workloads), Aria, MyRocks, ColumnStore for analytics, Spider for sharding, and S3 for archival, among others.
  • Replication and clustering. Asynchronous, semi-synchronous, and parallel replication with global transaction IDs, plus Galera synchronous multi-primary clustering.
  • Advanced SQL. Common table expressions and recursive CTEs, window functions, system-versioned (temporal) tables, sequences, and a broad set of JSON functions.
  • MySQL and Oracle compatibility. Wire-protocol and syntax compatibility with MySQL, plus an Oracle SQL mode supporting PL/SQL-style stored routines.
  • Spatial and full-text search. GIS data types and functions, and built-in full-text indexing.
  • Security. Role-based access control, pluggable authentication (ed25519, PAM, GSSAPI, and more), data-at-rest encryption, and TLS for connections.

Documentation

Releases

MariaDB Server follows a yearly long-term support (LTS) model alongside quarterly rolling releases. Binary LTS releases are maintained for three years and are recommended for production; rolling releases deliver new features sooner with a shorter support window.

For the current version and full history, see Releases and the MariaDB release calendar.

Installing

Packages and installation instructions for all supported platforms are available at https://mariadb.org/download/.

Building from source

To build MariaDB from source and run the test suite, follow the developer guide

It covers building the code correctly, running the MariaDB testing framework, and choosing the right branch to target for contributions.

Contributing

Contributions are welcome, from code and documentation to bug reports and reviews. See CONTRIBUTING.md to get started, and CODING_STANDARDS.md for code style. Contributors and community members are recognised in CREDITS.

Getting help

Licensing

MariaDB Server is licensed under version 2 of the GNU General Public License (GPLv2), without the "any later version" clause. This is inherited from MySQL. License information is in the COPYING file, and third-party license information is in the THIRDPARTY file.

About MariaDB Foundation

MariaDB is brought to you by the MariaDB Foundation and MariaDB plc. The MariaDB Foundation is the custodian of the MariaDB Server codebase, ensuring it stays open and that anyone can contribute. See CREDITS for details on the Foundation and the people developing MariaDB.

MySQL, the base of MariaDB, is a product and trademark of Oracle Corporation, Inc.

Description
Сервер MariaDB - это разработанный сообществом форк сервера MySQL
https://mariadb.org Readme 2.7 GiB
Languages
MariaDB\ 71.8%
C++ 16.5%
C 10.3%
Shell 0.5%
Perl 0.4%
Other 0.3%