[root@localhost mythtv]# mythbackend
2006-08-15 17:10:01.284 Using runtime prefix = /usr
2006-08-15 17:10:01.410 New DB connection, total: 1
2006-08-15 17:10:01.436 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:10:01.461 Current Schema Version: 1123
2006-08-15 17:10:01.484 Newest Schema Version : 1155
2006-08-15 17:10:01.485 New DB connection, total: 2
2006-08-15 17:10:01.486 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:10:01.487 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2006-08-15 17:10:01.489 New DB connection, total: 3
2006-08-15 17:10:01.489 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:10:01.491 Upgrading to schema version 1124
2006-08-15 17:10:01.582 New DB connection, total: 4
2006-08-15 17:10:01.583 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:10:01.601 Upgrading to schema version 1125
2006-08-15 17:10:01.632 Upgrading to schema version 1126
2006-08-15 17:10:01.660 Upgrading to schema version 1127
2006-08-15 17:10:01.684 Upgrading to schema version 1128
2006-08-15 17:10:01.719 Upgrading to schema version 1129
2006-08-15 17:10:01.761 New DB connection, total: 5
2006-08-15 17:10:01.762 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:10:01.764 Upgrading to schema version 1130
2006-08-15 17:10:01.774 Upgrading to schema version 1131
2006-08-15 17:10:01.791 Upgrading to schema version 1132
2006-08-15 17:10:01.808 Upgrading to schema version 1133
2006-08-15 17:10:01.828 Upgrading to schema version 1134
2006-08-15 17:10:01.830 Upgrading to schema version 1135
2006-08-15 17:10:01.888 Upgrading to schema version 1136
2006-08-15 17:10:06.395 Upgrading to schema version 1137
2006-08-15 17:10:06.643 Upgrading to schema version 1138
2006-08-15 17:10:06.645 Upgrading to schema version 1139
2006-08-15 17:10:06.707 Upgrading to schema version 1140
2006-08-15 17:10:06.709 Upgrading to schema version 1141
2006-08-15 17:10:06.813 Upgrading to schema version 1142
2006-08-15 17:10:06.814 DB Error (Performing database upgrade): 
Query was: CREATE TABLE customexample (  rulename VARCHAR(64) NOT NULL PRIMARY KEY,   fromclause text NOT NULL DEFAULT '',  whereclause text NOT NULL DEFAULT ''); 
Error was: Driver error was [2/1050]:
QMYSQL3: Unable to execute query
Database error was:
Table 'customexample' already exists
 
new version: 1142
2006-08-15 17:10:06.814 Database Schema upgrade failed, unlocking.
2006-08-15 17:10:06.815 Couldn't upgrade database to new schema
[root@localhost mythtv]# mythbackend
2006-08-15 17:10:30.566 Using runtime prefix = /usr
2006-08-15 17:10:30.601 New DB connection, total: 1
2006-08-15 17:10:30.610 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:10:30.615 Current Schema Version: 1141
2006-08-15 17:10:30.616 Newest Schema Version : 1155
2006-08-15 17:10:30.617 New DB connection, total: 2
2006-08-15 17:10:30.618 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:10:30.619 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2006-08-15 17:10:30.620 New DB connection, total: 3
2006-08-15 17:10:30.621 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:10:30.623 Upgrading to schema version 1142
2006-08-15 17:10:30.624 DB Error (Performing database upgrade): 
Query was: CREATE TABLE customexample (  rulename VARCHAR(64) NOT NULL PRIMARY KEY,   fromclause text NOT NULL DEFAULT '',  whereclause text NOT NULL DEFAULT ''); 
Error was: Driver error was [2/1050]:
QMYSQL3: Unable to execute query
Database error was:
Table 'customexample' already exists
 
new version: 1142
2006-08-15 17:10:30.625 Database Schema upgrade failed, unlocking.
2006-08-15 17:10:30.625 Couldn't upgrade database to new schema

[root@localhost mythtv]# mysql -p mythconverg                                   
Enter password: 
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 43 to server version: 4.1.20

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> drop table customexample;
Query OK, 0 rows affected (0.01 sec)

mysql> quit 
Bye
[root@localhost mythtv]# mythbackend                                     
2006-08-15 17:11:26.037 Using runtime prefix = /usr
2006-08-15 17:11:26.073 New DB connection, total: 1
2006-08-15 17:11:26.081 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:11:26.087 Current Schema Version: 1141
2006-08-15 17:11:26.088 Newest Schema Version : 1155
2006-08-15 17:11:26.089 New DB connection, total: 2
2006-08-15 17:11:26.090 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:11:26.091 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2006-08-15 17:11:26.092 New DB connection, total: 3
2006-08-15 17:11:26.093 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:11:26.095 Upgrading to schema version 1142
2006-08-15 17:11:26.134 New DB connection, total: 4
2006-08-15 17:11:26.135 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:11:26.137 Upgrading to schema version 1143
2006-08-15 17:11:26.168 Upgrading to schema version 1144
2006-08-15 17:11:26.180 Upgrading to schema version 1145
2006-08-15 17:11:26.191 Upgrading to schema version 1146
2006-08-15 17:11:26.196 Upgrading to schema version 1147
2006-08-15 17:11:34.780 Upgrading to schema version 1148
2006-08-15 17:11:34.952 Upgrading to schema version 1149
2006-08-15 17:11:35.023 Upgrading to schema version 1150
2006-08-15 17:11:35.038 Upgrading to schema version 1151
2006-08-15 17:11:35.096 Upgrading to schema version 1152
2006-08-15 17:11:36.316 Upgrading to schema version 1153
2006-08-15 17:11:40.010 DB Error (Performing database upgrade): 
Query was: INSERT INTO recordedseek (chanid, starttime, mark, offset, type) SELECT chanid, starttime, mark, offset, type FROM recordedmarkup WHERE type in (6, 7, 9); 
Error was: Driver error was [2/1062]:
QMYSQL3: Unable to execute query
Database error was:
Duplicate entry '1151-2006-08-05 08:30:00-6-1830' for key 1
 
new version: 1153
2006-08-15 17:11:40.010 Database Schema upgrade failed, unlocking.
2006-08-15 17:11:40.011 Couldn't upgrade database to new schema

[root@localhost mythtv]# mythbackend                                  
2006-08-15 17:14:53.217 Using runtime prefix = /usr
2006-08-15 17:14:53.363 New DB connection, total: 1
2006-08-15 17:14:53.388 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:14:53.418 Current Schema Version: 1152
2006-08-15 17:14:53.425 Newest Schema Version : 1155
2006-08-15 17:14:53.426 New DB connection, total: 2
2006-08-15 17:14:53.427 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:14:53.428 Setting Lock for Database Schema upgrade. If you see a long pause here it means the Schema is already locked and is being upgraded by another Myth process.
2006-08-15 17:14:53.437 New DB connection, total: 3
2006-08-15 17:14:53.438 Connected to database 'mythconverg' at host: localhost
2006-08-15 17:14:53.441 Upgrading to schema version 1153
2006-08-15 17:14:56.618 DB Error (Performing database upgrade): 
Query was: INSERT INTO recordedseek (chanid, starttime, mark, offset, type) SELECT chanid, starttime, mark, offset, type FROM recordedmarkup WHERE type in (6, 7, 9); 
Error was: Driver error was [2/1062]:
QMYSQL3: Unable to execute query
Database error was:
Duplicate entry '1168-2006-08-09 00:00:00-6-4538' for key 1
 
new version: 1153
2006-08-15 17:14:56.618 Database Schema upgrade failed, unlocking.
2006-08-15 17:14:56.619 Couldn't upgrade database to new schema
[root@localhost mythtv]#