Closed Bug 996228 Opened 12 years ago Closed 12 years ago

Schematic: use MySQL-python instead of forking mysql subprocesses

Categories

(addons.mozilla.org Graveyard :: Code Quality, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
2014-05

People

(Reporter: oremj, Assigned: yboniface)

Details

Right now, schematic runs "mysql -u foo -ppass -h db_host db_name". In MySQL 5.6, -p throws a warning and breaks schematic. We need to use MySQL-python instead of avoid the errors.
Assignee: nobody → yboniface
Longer term, we should move to South or Django 1.7, as per bug 905785.
I don't think this will be a problem, given the situation of schematic (old and unmaintained, plus untested), but just to make it explicit: I'm going to make schematic MySQL specific, even though it's not really the case now. Please stop me if this is not wanted.
That's a good point. Alternatively, we could change: if config['PASSWORD']: s += ' -p{PASSWORD}' to: os.environ['MYSQL_PWD'] = config['PASSWORD'] in schematic settings.
(In reply to Jeremy Orem [:oremj] from comment #4) > That's a good point. Alternatively, we could change: > if config['PASSWORD']: > s += ' -p{PASSWORD}' > to: > os.environ['MYSQL_PWD'] = config['PASSWORD'] > > in schematic settings. That seems super easy. Let's just do that..
@oremj are you pushing to olympia too?
Sure, I think solitude and webpay need it as well. Anything else?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2014-05
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.