MySQL transactions help maintain data consistency by grouping related SQL updates so they can be committed together or rolled back when an operation fails. See how START TRANSACTION and ROLLBACK work with inventory updates and database constraints to reverse uncommitted changes, and explore the MySQL transaction documentation: https://dev.mysql.com/doc/refman/26.10/en/commit.html
The latest from the MySQL community
Ideas, releases, practical guides, and perspectives from the people building with MySQL.
We've heard positive feedback about VillageSQL's documentation, so we wanted to share a bit more on how we build it and how we hope to evolve it. VillageSQL Server tracks upstream MySQL and adds an extension framework, so the documentation has two moving targets. We pull in upstream changes with each MySQL release, and VillageSQL's own changes land daily in the dev branch and ship with each release. We believe that it's important for a complex project to provide accurate documentation that is updated as frequently as code ships. This is easier said than done. We use AI extensively to generate our docs, but we believe it's critical to have a human as a review gate before any change is shipped. AI makes mistakes, so we make it prove every change to itself and to humans by testing against a running server.
Frequent readers of the VillageSQL docs will also notice a recent redesign. The …
[Read more]Some of the first large database servers I worked with were DEC VAX/VMS systems running Sybase. They were physically huge machines. Towers of quad 90.91 MHz processors, with more towers beside them holding mirrored RAID5 storage. At the time, this was big iron, taking food stamps in Texas to debit cards. A lot has changed […]
From Big Iron to AMD EPYC: Preparing TAF to Push MariaDB at Scale appeared first on MariaDB.org
Your Amazon Aurora MySQL cluster looks healthy. Reads and writes
succeed and every metric is green. Then a routine CREATE
INDEX fails with error 63955, and from then on no index
that includes a virtual column can be created on the cluster
until you rebuild its databases.
Error Code: 63955.
Index cannot be created because virtual index ID limit (4294967295) was reached.
-
What it means: the cluster has used up the
internal IDs Aurora MySQL uses when it evaluates indexes that
contain a virtual column. This error does not affect existing
data or ordinary indexes, but new indexes on
VIRTUALgenerated columns, functional indexes, and multi-valued indexes fail. -
What helps short term: converting the
generated column in the failing index from
VIRTUALtoSTORED, so that the index no longer contains a …
Welcome back to Village News, our curated roundup of MySQL and database news. This week, PostgreSQL shipped updates fixing 52 security vulnerabilities and retired PostgreSQL 14, and the FOSDEM M-Ecosystem devroom opened its call for participation.
If you want to get these updates, just subscribe to the blog.
Enjoy!
MySQL News
Note: Aggregated MySQL news can be found at Planet for MySQL Community and Planet MySQL (Oracle curated)
Just Because You Can, Doesn’t Mean You Should:
Re-evaluating Galera Node Weights
…
We all know that when using a cluster based on Galera (Codership) such as Percona XtraDB Cluster (PXC), it is recommended to deploy an odd number of nodes.
The generic answer to this recommendation is that otherwise the risk of having an inconsistent cluster (like split-brain) is higher. (see Get started with Percona XtraDB Cluster – Percona XtraDB Cluster )
As a reminder, when split-brain occurs, a cluster will stop accepting queries, which is what a safe solution should do while waiting for the DBA to review and decide which of the two nodes is the leader. I do not even want to describe the infamous wsrep_provider_options=”pc.ignore_sb = yes”, which has been the cause of many, many nights spent trying to …
[Read more]MySQL's LAG() window function helps you compare sales totals across rows and calculate changes between consecutive records. See how to retrieve previous row values, order sales data by date, and calculate sales differences using the LAG() function in MySQL: https://dev.mysql.com/doc/refman/26.10/en/window-function-descriptions.html#function_lag
It’s Thursday afternoon, and a developer has an idea.
Nothing complicated. They are working on a new application feature and want to test an idea before committing to a larger implementation. A quick prototype is already running locally. So far, so good. Next, they want to deploy the application to a shared environment so their colleagues can try it out. The application needs a database too, but it needs to be accessible from the shared environment, not just their laptop. And that’s where things get more complicated.
Now they need to submit a request to the infrastructure team, wait for an environment to be provisioned, or spend the afternoon working through Kubernetes configurations. What should have been a quick experiment becomes another task on somebody else’s backlog.
This is a common problem for engineering teams. Getting a database running in a shared environment shouldn’t require extensive coordination or …
[Read more]Multi-tenant software as a service (SaaS) applications regularly need to copy one tenant’s data from production into a lower environment. Teams do this to reproduce a defect, validate a schema change, or give quality assurance (QA) a representative dataset. When production and non-production run in separate AWS accounts, their virtual private clouds (VPCs) often have no route to each other. That turns the copy into a networking problem as much as a data problem, and security teams are rightly reluctant to open a path between the two.
In this post, we show how to move a single tenant’s data between
Amazon Aurora MySQL-Compatible Edition clusters in two separate
AWS accounts, using Aurora cloning, SELECT INTO OUTFILE
S3, and LOAD DATA FROM S3. The databases
don’t connect directly. Each account reaches Amazon Simple
Storage Service (Amazon S3) independently through its own gateway
VPC endpoint, and the accounts …