If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Update Pootle DB to latest SVN trunk format

RESOLVED FIXED

Status

Webtools Graveyard
Verbatim
RESOLVED FIXED
8 years ago
2 years ago

People

(Reporter: wenzel, Unassigned)

Tracking

Details

(Reporter)

Description

8 years ago
I `svn up`ped the Verbatim Alpha instance of Pootle and needless to say the database format apparently changed drastically since we last did that.

I have yet to find documentation on how to update Pootle's DB without losing data, so this is the bug for that.

If worse comes to worst, I'll need to regenerate an empty DB and cherry-pick data from the broken DB to somehow import into the new one. :(
(Reporter)

Comment 1

8 years ago
I recreated a blank DB, then created the AMO project again. It came back and seems to work -- I dumped the old sqlite database to see what useful data it contained, but there were no user rights in there, so I call this one closed for now.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Reporter)

Updated

8 years ago
Blocks: 502215
No longer depends on: 502215
User rights are pre-sqlite.  There is a mysql database on there that holds the rights.
(Assignee)

Updated

2 years ago
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.