This post is the fourth post of a series of articles on extending MySQL with the Component Infrastructure, the list above will be updated as new articles are published:
What is Schema Tracking? # In a distributed relational database system, like Vitess, a central component is responsible for serving queries across multiple shards. For Vitess, it is VTGate. One of the challenges this component faces is being aware of the underlying SQL schema being used. This awareness facilitates query planning. Table schemas are stored in MySQL’s information_schema, meaning that they are located in a VTTablet’s MySQL instance and not in VTGate.
On Twitter, Jan Wildeboer linked
on MySQL and the weird utf8mb4 character set.
The recommendation is correct:
In MySQL, use utf8mb4 when you mean to work with
utf8 in your programming language.
The background and reasoning for this (and why it is wrong) is way more complicated than outlined by Adam Hooper. So let’s walk through this:
MySQL utf8 means 3-byte Unicode, and
access to only the BMP
utf8 in MySQL encodes the …
We have planned for archiving the data to improve the DB performance and to reclaim the space. We were evaluating Compression in InnoDB and TokuDB. To find out the best compression method. We started benchmarking the compression ratio between InnoDB and TokuDB.
Everything goes well for some time, but after a few hours got an error message that can’t able to insert the data into the TokuDB table due to storage being full. It is so strange and the host has enough free space.
Table structure:-
mysql> show create table mydbops.tokudb\G
*************************** 1. row ***************************
Table: tokudb
Create Table: CREATE TABLE `tokudb` (
`ID` int DEFAULT NULL,
`Name` longtext,
`Image` blob
) ENGINE=TokuDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
1 row in set (2.18 sec)
mysql> show create table mydbops.innodb\G
*************************** 1. row …[Read more]
It’s that time once again. I’ve published another issue of OpenLamp.tech, the newsletter for PHP/MySQL developers, over the weekend with all the curated content for your reading experience. There is plenty to learn for everyone so dig in…
I start my day every day with Refind. You should too.
Self-Promotion:
If you enjoy the content written here, by all means, share this blog and your favorite post(s) with others who may benefit from or like it as well. Since coffee is my favorite drink, you can even buy me one if you would like!
This week in the OpenLamp.tech newsletter, we have articles covering:
This post is the third post of a series of articles on extending MySQL with the Component Infrastructure:
This post is the second post of a series of articles on extending MySQL with the Component Infrastructure:
Includes the new product features and releases, top webinars, top blogs, top customer references, top videos, top white papers and more from 2021.
This post is the first post of a series of articles on extending MySQL with the Component Infrastructure, the list above will be updated as new articles are published:
With modern application design, systems are becoming more diverse, varied and have more components than ever before. Developers are often forced to become master chefs adding the ingredients from dozens of different technologies and blending them together to create something tasty and amazing. But with so many different ingredients, it is often difficult to understand how the individual ingredients interact with each other. The more diverse the application, the more likely it is that some seemingly insignificant combination of technology may cause cascading effects.
Many people I talk to have hundreds if not thousands of different libraries, APIs, components, and services making up the systems they support. In this type of environment, it is very difficult to know what small thing could add up to something much bigger. Look at some of the more recent …
[Read more]