Today, I had an alert on a #servicenow self-hosted database running on #MySQL with 1TB of RAM and 18TB of NVMe (in RAID10-like). 100% i/o write usage. 3k connections. Why on earth do we need that amount of resources? There must be something wrong in the design.
I'm looking for a solution to branch-based previews for a #PHP / #MySQL stack. We have nearly 60 sites we want to set this up for (a lot of services I find either charge $1000s or don't even support that many).
I don't want anything fancy, I don't need to edit in the browser. I would like to push a branch to gitlab and have the option to spin up an environment to preview.
I have considered doing it myself, but I was hoping to not have to support my own infrastructure.
For my #blog, I also observed this problem. This is not very disturbing, but after publishing information about the new post, the site temporarily stops working and throws the error of exceeding the #MySQL query limit, because the blog is based, of course, on #Wordpress.
via #unknowNews https://news.itsfoss.com/mastodon-link-problem/
An instance of a popular CMS is used for a website. While analyzing I'm coming across a a table in it's MySQL database where a column called "deleted" is defined as such:
deleted` tinyint(4) NOT NULL DEFAULT 0 COMMENT 'A boolean indicating whether this data item has been deleted‘
🤦♂️
There should be a license allowing allowed to write software used by someone else. Like with drivers licenses it needs a points system for violations and license revocation. #WebDevelopment#PHP#MYSQL#SQL
TIL: If you try to manually INSERT a row into a MySQL table and set an AUTO_INCREMENT column to 0, MySQL ignores the provided value and assumes you want the next increment amount.
Found this whilst migrating a legacy database to a new structure, where the legacy database had foreign keys (not actually defined as constraints) with 0 values.
You can control this with NO_AUTO_VALUE_ON_ZERO in sql_mode (it's on by default I think).
Post en français ici. TL;DR: Older versions of Drupal does not work with MySQL 8.0. Update now. Brace yourself, MySQL 8.0 is coming soon on the databases delivered with your web hostings, also called "SharedSQL" (more info soon). After my post on old Wordpress, this one is about old Drupal. Issue Whether you installed it...
MySQL folks take a lot of things for granted that are not present in this form in Postgres, and that may be a bad surprise when you try out "the other system".
MySQL for example has a stable and upwards- and slightly-downwards-compatible on-disk format, mostly. Oracle sometimes forgets how important that is and makes changes, or unannounced changes, and then needs to be corrected, hard, by their development partners and testers.
@isotopp I definitely prefer PostgreSQL to #MySQL, but #PostgreSQL deciding that collation derives from your system's locale settings when PostgreSQL installed means identical setups on different boxes can behave differently. This is NOT FUN to debug.
I've heard that there was discussion to change this, but I don't know if it happened.
Very nice tool for converting an #SQLite database into #MySQL: https://github.com/techouse/sqlite3-to-mysql. I'm planning to experiment with switching from SQLite to MySQL or Postgres (and maybe DuckDB?) for the feeds database and see how it behaves and how the performance differs… 🤔
There's like an entire class of open source project where you can no longer get support for them because they're old enough that the support channels are IRC rather than Discord or something but nobody's on IRC anymore (or rather hundreds of people are on the libera.chat channel, but no one is talking or reading questions)
Anyway I upgraded Ubuntu and now mysql is in a boot loop where it starts up, prints "Starting upgrade of data directory", prints "table SPECIFIC_TABLE_THAT_SHOULD_BE_THERE not found in InnoDB dictionary", then prints "aborting" and the process begins again. Most of the repair tools for mysql seem to assume the mysqld is already running rather than in a boot loop. There are 210 people in the #mysql irc channel on Libera and no one but me is talking. I'm not actually sure where to begin here!
MySQL 8.0: Prepare your old Drupal (community.ovh.com)
Post en français ici. TL;DR: Older versions of Drupal does not work with MySQL 8.0. Update now. Brace yourself, MySQL 8.0 is coming soon on the databases delivered with your web hostings, also called "SharedSQL" (more info soon). After my post on old Wordpress, this one is about old Drupal. Issue Whether you installed it...