Bug 677932 - [abrt] translate-toolkit-1.8.1-1.fc14: tmdb.py:116:init_database:OperationalError: database schema has changed
Summary: [abrt] translate-toolkit-1.8.1-1.fc14: tmdb.py:116:init_database:OperationalE...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: translate-toolkit
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dwayne Bailey
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bdc77e95
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 10:06 UTC by Dave Galloway
Modified: 2012-06-06 08:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 08:04:02 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (1.94 KB, text/plain)
2011-02-16 10:06 UTC, Dave Galloway
no flags Details

Description Dave Galloway 2011-02-16 10:06:15 UTC
abrt version: 1.1.14
architecture: x86_64
cmdline: /usr/bin/python /usr/bin/tmserver -b localhost -p 55555 -d /home/DaveMatel8888/.virtaal/tm.db --min-similarity=70 --max-candidates=5
component: translate-toolkit
executable: /usr/bin/tmserver
kernel: 2.6.35.10-74.fc14.x86_64
package: translate-toolkit-1.8.1-1.fc14
reason: tmdb.py:116:init_database:OperationalError: database schema has changed
release: Fedora release 14 (Laughlin)
time: 1296137039
uid: 500

backtrace
-----
tmdb.py:116:init_database:OperationalError: database schema has changed

Traceback (most recent call last):
  File "/usr/bin/tmserver", line 27, in <module>
    tmserver.main()
  File "/usr/lib/python2.7/site-packages/translate/services/tmserver.py", line 194, in main
    prefix="/tmserver", source_lang=options.source_lang, target_lang=options.target_lang)
  File "/usr/lib/python2.7/site-packages/translate/services/tmserver.py", line 49, in __init__
    self.tmdb = tmdb.TMDB(tmdbfile, max_candidates, min_similarity, max_length)
  File "/usr/lib/python2.7/site-packages/translate/storage/tmdb.py", line 66, in __init__
    self.init_database()
  File "/usr/lib/python2.7/site-packages/translate/storage/tmdb.py", line 116, in init_database
    self.cursor.executescript(script)
OperationalError: database schema has changed

Local variables in innermost frame:
self: <translate.storage.tmdb.TMDB object at 0x26ba090>
script: '\nCREATE TABLE IF NOT EXISTS sources (\n       sid INTEGER PRIMARY KEY AUTOINCREMENT,\n       text VARCHAR NOT NULL,\n       context VARCHAR DEFAULT NULL,\n       lang VARCHAR NOT NULL,\n       length INTEGER NOT NULL\n);\nCREATE INDEX IF NOT EXISTS sources_context_idx ON sources (context);\nCREATE INDEX IF NOT EXISTS sources_lang_idx ON sources (lang);\nCREATE INDEX IF NOT EXISTS sources_length_idx ON sources (length);\nCREATE UNIQUE INDEX IF NOT EXISTS sources_uniq_idx ON sources (text, context, lang);\n\nCREATE TABLE IF NOT EXISTS targets (\n       tid INTEGER PRIMARY KEY AUTOINCREMENT,\n       sid INTEGER NOT NULL,\n       text VARCHAR NOT NULL,\n       lang VARCHAR NOT NULL,\n       time INTEGER DEFAULT NULL,\n       FOREIGN KEY (sid) references sources(sid)\n);\nCREATE INDEX IF NOT EXISTS targets_sid_idx ON targets (sid);\nCREATE INDEX IF NOT EXISTS targets_lang_idx ON targets (lang);\nCREATE INDEX IF NOT EXISTS targets_time_idx ON targets (time);\nCREATE UNIQUE INDEX IF NOT EXISTS targets_uniq_idx ON targets (sid, text, lang);\n'

How to reproduce
-----
1.just errered on its own
2.
3.

Comment 1 Dave Galloway 2011-02-16 10:06:17 UTC
Created attachment 479071 [details]
File: backtrace

Comment 2 Dwayne Bailey 2011-02-17 06:52:57 UTC
Thanks for the buf report.  It would help us solve this correctly if you can get us the following information:

1) Could you please run the following commands so that we can get a dump of the TM schema:

sqlite3 ~/.virtaal/tm.db ".schema" > schema.sql

Then attach "schema.sql" to this bug.

2) What was the previous version of translate-toolkit that was running on your machine?

Comment 3 Dwayne Bailey 2011-02-17 06:58:32 UTC
The bug has been reported upstream http://bugs.locamotion.org/show_bug.cgi?id=1875

Note you can also safely remove ~/.virtaal/tm.db - please don't do it before you've created the dump.  It will mean you lose any existing TM but this will rebuild as you translate in Virtaal.

Comment 4 Dwayne Bailey 2011-02-23 13:28:41 UTC
From upstream....

More information might be useful here:

A possible explanation might be that two Virtaal/tmserver processes got
launched at about the same time and both tried to create the TM database. If
this was the error obtained on first run (or first 2 runs) this sounds
possible.

Other possibilities include recent upgrades to any of these: python, sqlite or
pysqlite.

Also, is this error persistent, or did it disappear when running Virtaal again?

Please can you provide feedback

Comment 5 Akira TAGOH 2011-12-05 11:09:23 UTC
Any updates?

Comment 6 Akira TAGOH 2012-06-06 08:04:02 UTC
Please reopen with the certain information if you still see this issue. thanks.


Note You need to log in before you can comment on or make changes to this bug.