Submitted Aug 14, 2019

Supporting utf8 characters in a utf8 mysql table

Section: Crisp talk (20 mins) Category: DevOps

This proposal has been added to the schedule

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

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

Requirements

Speaker bio

Lead Software Engineer @ Freshworks.

Comments

Up next

Demystifying AIOps

For years, IT has struggled to keep the lights on. Now that businesses are aggressively pursuing digital transformation, that battle is becoming even more difficult. The number of applications and services is exploding. Changes are now measured in seconds or minutes, instead of months or years. Approaches such as DevOps are driving this acceleration – but, unless IT operations can keep up, digitalization will inevitably hit a brick wall.

Aug 7, 2019

Rootconf Hyderabad edition