444621 - Pootle needs to use a mysql database

Status: RESOLVED FIXED

(Webtools Graveyard :: Verbatim, defect)

Description

[Wil Clouser [:clouserw]]

Pootle looks for .stats files right and if those don't exist it looks for the sqlite db that pocount makes.  We need to make it use mysql.

Comment 1

[Friedel Wolff]

In as much as I can see bug 444620 will address this entirely. The only issue might be to specify database connection information. The statistics code is really shared between pocount and Pootle. There should be very little work necessary on the Pootle side.

Comment 2

[Dan Schafer [:dschafer]]

As I envision it, part of this is moving as much data storage as possible from flat files to the database.  For example, the information in project .prefs files in each directory, pootle.prefs, and users.prefs should all be in the database.  I've arbitrarily been using bug 444620 for patches involving stats; we could use this bug for non-stats patches.

Comment 4

[Dan Schafer [:dschafer]]

From Bug 446443:

Users, projects, stats, languages, rights and goals should all be converted
from flat files to databases; since this is such a large task, these are all
listed in sub-bugs.

All but the rights / goals / assigns are done, and those are fairly minor features, so I'm removing the priority from this.

Comment 5

[Wil Clouser [:clouserw]]

bug 446441, bug 447819, and bug 449132 cover the remaining issues.  Since pootle+django can use mysql I'm closing this.