Rootconf Hyderabad edition

On SRE, systems engineering and distributed systems

Supporting utf8 characters in a utf8 mysql table

Submitted by Ritikesh (@ritikesh) on Aug 14, 2019

Section: Crisp talk (20 mins) Category: DevOps Status: Confirmed & scheduled

Abstract

Abstract:

MySQL’s “utf8” encoding only supports three bytes per character. The real UTF-8 encoding needs up to four bytes per character. After upgrading our app’s rails version in production, we started noticing issues in saving objects in the database because of MySQL’s strict mode. We’ll talk about key learnings, the migration itself and best practises for newer apps.

Target Audience:

Developers/Devops Engineers

Outline

  1. How we supported storing utf8 content in our app.
  2. How upgrading the rails version caused MySQL to run in strict mode causing the problems.
  3. How we evaluated our options and chose the final solution.
  4. The actual migration and dealing with ad-hoc issues.

Requirements

NA

Speaker bio

Lead Software Engineer @ Freshworks.

Links

Comments

{{ gettext('Login to leave a comment') }}

{{ gettext('You need to be a participant to comment.') }}

{{ formTitle }}
{{ gettext('Post a comment...') }}
{{ gettext('New comment') }}

{{ errorMsg }}