Bug 1023944

Summary: Document how to change MySQL character set configuration
Product: OKD Reporter: Hiro Asari <hasari>
Component: DocumentationAssignee: Julie <juwu>
Status: CLOSED NEXTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.xCC: jkeck, lmeyer, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-04 00:04:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Hiro Asari 2013-10-28 12:09:05 UTC 
Description of problem:
Describe how to change MySQL character set for the session.

Bug 1010582 describes how to change MySQL instance's character set with action hooks, application configurations, etc.
Comment 3 Luke Meyer 2014-02-24 14:05:59 UTC 
It's a request for enhancement/clarification. And yes, I'd say it's legitimate; it's an instance where using something (MySQL) under OpenShift is not as straightforward as people are used to when running it independently and having full control over the configuration. Our answer in this case seems to be that really, it's something your DB client usage should specify anyway. Although it's possible to specify the setting globally in a git action hook, that doesn't seem like a good recommendation to make.

I'm not sure at this time where exactly in the user guide this should go. If there's a section for MySQL-specific notes, then some mention of the the need for the client to specify character set, with a reference to bug 1010582 would be a good addition.
Comment 12 Julie 2014-04-04 00:04:41 UTC 
updates already published in Online User Guide.
Enterprise User Guide pending next release.