portfolio.robn.au/fixing/mysql-character-sets

Preview meta tags from the portfolio.robn.au website.

Linked Hostnames

2

Search Engine Appearance

Google

https://portfolio.robn.au/fixing/mysql-character-sets

MySQL character sets and storing "high" characters

This is the text of an email sent to one of Fastmail's internal engineering lists, and has been sanitised slightly to remove private information and internal links. Since 1999, Fastmail has used MySQL as its internal database. In those days it was famous for its lack of robustness, and over the years Fastmail has built up a layer of workarounds to correct for this. In 2021 I began a project to upgrade from MySQL 5.1 (2008!) to MySQL 8. MySQL these days is good enough that most of the workarounds were now in the way, and so had to be carefully removed or worked around. This is the story of just one of them.



Bing

MySQL character sets and storing "high" characters

https://portfolio.robn.au/fixing/mysql-character-sets

This is the text of an email sent to one of Fastmail's internal engineering lists, and has been sanitised slightly to remove private information and internal links. Since 1999, Fastmail has used MySQL as its internal database. In those days it was famous for its lack of robustness, and over the years Fastmail has built up a layer of workarounds to correct for this. In 2021 I began a project to upgrade from MySQL 5.1 (2008!) to MySQL 8. MySQL these days is good enough that most of the workarounds were now in the way, and so had to be carefully removed or worked around. This is the story of just one of them.



DuckDuckGo

https://portfolio.robn.au/fixing/mysql-character-sets

MySQL character sets and storing "high" characters

This is the text of an email sent to one of Fastmail's internal engineering lists, and has been sanitised slightly to remove private information and internal links. Since 1999, Fastmail has used MySQL as its internal database. In those days it was famous for its lack of robustness, and over the years Fastmail has built up a layer of workarounds to correct for this. In 2021 I began a project to upgrade from MySQL 5.1 (2008!) to MySQL 8. MySQL these days is good enough that most of the workarounds were now in the way, and so had to be carefully removed or worked around. This is the story of just one of them.

  • General Meta Tags

    5
    • title
      MySQL character sets and storing "high" characters · Fixing · Rob Norris · Systems Programmer
    • charset
      utf-8
    • viewport
      width=device-width, initial-scale=1
    • article:section
      fixing
    • fediverse:creator
  • Open Graph Meta Tags

    6
    • og:url
      https://portfolio.robn.au/fixing/mysql-character-sets/
    • og:site_name
      Rob Norris · Systems Programmer
    • og:title
      MySQL character sets and storing "high" characters
    • og:description
      This is the text of an email sent to one of Fastmail's internal engineering lists, and has been sanitised slightly to remove private information and internal links. Since 1999, Fastmail has used MySQL as its internal database. In those days it was famous for its lack of robustness, and over the years Fastmail has built up a layer of workarounds to correct for this. In 2021 I began a project to upgrade from MySQL 5.1 (2008!) to MySQL 8. MySQL these days is good enough that most of the workarounds were now in the way, and so had to be carefully removed or worked around. This is the story of just one of them.
    • US country flagog:locale
      en_us
  • Twitter Meta Tags

    3
    • twitter:card
      summary
    • twitter:title
      MySQL character sets and storing "high" characters
    • twitter:description
      This is the text of an email sent to one of Fastmail's internal engineering lists, and has been sanitised slightly to remove private information and internal links. Since 1999, Fastmail has used MySQL as its internal database. In those days it was famous for its lack of robustness, and over the years Fastmail has built up a layer of workarounds to correct for this. In 2021 I began a project to upgrade from MySQL 5.1 (2008!) to MySQL 8. MySQL these days is good enough that most of the workarounds were now in the way, and so had to be carefully removed or worked around. This is the story of just one of them.
  • Link Tags

    6
    • me
      https://social.lol/@robn
    • me
      https://robn.au/
    • stylesheet
      /css/site.css
    • stylesheet
      /css/fontawesome.min.css
    • stylesheet
      /css/brands.min.css

Links

6