Today’s bug: I tried to store a UTF-8 string in a MariaDB “utf8”-encoded database, and Rails raised a bizarre error:

The problem is that MariaDB has to go the the trouble to implement the bugs in MySQL, as it aims to be a drop-in replacement. It’s far better to use postgres because its not held back by a proprietary BS counterpart.

As a DB Adminitrator which is part of my SysAdmin curriculum I tell you.

  • MariaDB has nothing to do from MySQL development from a lot. It is independent.

  • utf8 was maintained for compatibility as an alias to utf8mb3 but can be changed in configuration to point utf8mb4.

  • Default configuration and several SQL sentences have changed compared to MySQL.

I tell you this by direct experience in the process of learning by using MariaDB and my classmates using MySQL.

Create a post

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

  • Posts must be relevant to the open source ideology
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

  • 0 users online
  • 5 users / day
  • 14 users / week
  • 19 users / month
  • 6 users / 6 months
  • 22 subscribers
  • 584 Posts
  • 1.24K Comments
  • Modlog