Project

General

Profile

Bug #552

Downgrading DB borks database without warning

Added by kitterma almost 16 years ago. Updated almost 16 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/12/2009
Due date:
% Done:

100%

Estimated time:
Version:
0.3.1+
OS:
Any

Description

Because of the problems I was having with my Feb 11 git snapshot core, I downgraded to Feb 6 core and then got:

2009-02-12 13:51:58 Error: Installed Schema is newer then any known Version.
2009-02-12 13:51:58 Error: unhandled Error in QSqlQuery!
2009-02-12 13:51:58 Error: last Query: "CREATE TABLE quasseluser ( userid INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, username TEXT UNIQUE NOT NULL, password TEXT NOT NULL)"
2009-02-12 13:51:58 Error: executed Query: ""
2009-02-12 13:51:58 Error: bound Values:
2009-02-12 13:51:58 Error: Error Number: 1
2009-02-12 13:51:58 Error: Error Message: "table quasseluser already exists Unable to execute statement"
2009-02-12 13:51:58 Error: Driver Message: "Unable to execute statement"
2009-02-12 13:51:58 Error: DB Message: "table quasseluser already exists"
2009-02-12 13:51:58 Error: Unable to setup Logging Backend!
2009-02-12 13:51:58 Error: Could not init storage!
2009-02-12 13:52:09 Info: Non-authed client disconnected. 72.81.252.22
2009-02-12 13:52:09 Info: Listening for GUI clients on IPv4 0.0.0.0 port 4242 using protocol version 9
2009-02-12 13:52:38 Info: Client connected from 72.81.252.22
2009-02-12 13:52:38 Info: Closing server for basic setup.
2009-02-12 13:52:52 Error: Installed Schema is newer then any known Version.
2009-02-12 13:52:52 Error: unhandled Error in QSqlQuery!
2009-02-12 13:52:52 Error: last Query: "CREATE TABLE quasseluser ( userid INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT, username TEXT UNIQUE NOT NULL, password TEXT NOT NULL)"
2009-02-12 13:52:52 Error: executed Query: ""
2009-02-12 13:52:52 Error: bound Values:
2009-02-12 13:52:52 Error: Error Number: 1
2009-02-12 13:52:52 Error: Error Message: "table quasseluser already exists Unable to execute statement"
2009-02-12 13:52:52 Error: Driver Message: "Unable to execute statement"
2009-02-12 13:52:52 Error: DB Message: "table quasseluser already exists"
2009-02-12 13:52:52 Error: Unable to setup Logging Backend!
2009-02-12 13:52:52 Error: Could not init storage!

So then I upgraded back to the Feb 11 version and still got the same error.

Associated revisions

Revision bb799766 (diff)
Added by Marcus Eggenberger almost 16 years ago

Fixes #552 - Don't try to use DBs with a too new schema version

History

#1 Updated by EgS almost 16 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#2 Updated by EgS almost 16 years ago

Obviously this fix doesn't help if you start any version of quassel prior to this commit.
Also I want to point out that, the DB was never in a corrupted state here.

Also available in: Atom PDF