Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
  • Sign in
G
gracedb
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 89
    • Issues 89
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • lscsoft
  • gracedb
  • Issues
  • #174

Closed
Open
Opened Sep 20, 2019 by Tanner Prestegard@tanner.prestegard
  • Report abuse
  • New issue
Report abuse New issue

Potential character set issue

The development and playground databases should have the correct character sets and collations due to how they were created by Puppet. But the production database was created so long ago that it looks like it has the latin1 character set by default.

It's not posing a problem at present since we have a migration which manually sets the auth_user table to use utf8, but I think it would be a good idea to set the database default character set and collation when an opportunity arises.

We'll have to get MySQL command-line access to the production database, then run:

ALTER DATABASE <dbname> CHARACTER SET utf8 COLLATE utf8_general_ci;

Might be worth testing this (I haven't) and taking a snapshot before doing so.

Related issues

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
database
Assign labels
  • View project labels
Reference: lscsoft/gracedb#174