0.10~beta2 and old sqlite database

[colo]

What's the best way to use the latest experimental build with a 0.99 sqlite database?

Thanks

[mike]

Make a backup ("File" -> "Save as"), uninstall the old version, install the new version.
If you like the beta, then there is nothing more to do.
If you want back to the 0.9.9, uninstall the beta, remove the data directory (Windows: "%APPDATA%\griffth")
install the 0.9.9 version, restore the backuped database ("File" -> "Revert").

Michael

[colo]

Am on Ubuntu Jaunty Beta/AMD64..

0.10~beta2 starts only when I delete the 0.99 version .griffith from my home folder. When I try and restore the 0.99 backup in 0.10~beta2, it crashes.

On another note, python-pysqlite2_2.5-2 in jaunty does not allow record saving if the data contains european characters, and python-pysqlite2_2.4-1 cannot be installed in jaunty.

[mike]

Please start griffith with the parameter "--debug" from the console and reproduce the crash.
After that post the output here. Thanks.

[colo]

d@d-ubuntu:~$ griffith --debug
DEBUG:Griffith:Starting Griffith 0.10-beta2
DEBUG:Griffith:Platform: Linux-2.6.28-11-generic-x86_64-with-Ubuntu-9.04-jaunty (posix)
DEBUG:Griffith:Dependencies:
gtk :: 2.14.1
gtk.glade :: 2.14.1
sqlalchemy :: 0.5.2
sqlite3 :: 2.4.1
reportlab :: 2.3
PIL :: True
psycopg2 :: 2.0.8 (dec mx dt ext pq3)
MySQLdb :: 1.2.2.final.0
chardet :: 1.0.1
sqlite :: False
DEBUG:Griffith:config file used: /home/d/.griffith/griffith.cfg
INFO:Griffith:Using Griffith directory: /home/d/.griffith
INFO:Griffith:Upgrading database to version 3...
Traceback (most recent call last):
  File "/usr/bin/griffith", line 1477, in <module>
    griffith = Griffith(home_dir, config)
  File "/usr/bin/griffith", line 106, in __init__
    self.db = GriffithSQL(config, self.locations['home'], self.locations)
  File "/usr/share/griffith/lib/sql.py", line 148, in __init__
    if not upgrade_database(self, v, locations, config):
  File "/usr/share/griffith/lib/dbupgrade.py", line 132, in upgrade_database
    db.ratios_table.insert(bind=b).execute(name=u'16:9')
  File "/var/lib/python-support/python2.6/sqlalchemy/sql/expression.py", line 1141, in execute
    return e._execute_clauseelement(self, multiparams, params)
  File "/var/lib/python-support/python2.6/sqlalchemy/engine/base.py", line 1209, in _execute_clauseelement
    return connection._execute_clauseelement(elem, multiparams, params)
  File "/var/lib/python-support/python2.6/sqlalchemy/engine/base.py", line 874, in _execute_clauseelement
    return self.__execute_context(context)
  File "/var/lib/python-support/python2.6/sqlalchemy/engine/base.py", line 896, in __execute_context
    self._cursor_execute(context.cursor, context.statement, context.parameters[0], context=context)
  File "/var/lib/python-support/python2.6/sqlalchemy/engine/base.py", line 950, in _cursor_execute
    self._handle_dbapi_exception(e, statement, parameters, cursor, context)
  File "/var/lib/python-support/python2.6/sqlalchemy/engine/base.py", line 931, in _handle_dbapi_exception
    raise exc.DBAPIError.instance(statement, parameters, e, connection_invalidated=is_disconnect)
sqlalchemy.exc.IntegrityError: (IntegrityError) column name is not unique u'INSERT INTO ratios (name) VALUES (?)' [u'16:9']

[mike]

It seems to me that you tried beta 1 before with the same database. Perhaps switch back to 0.9.9 and than forward to beta 2.
The main problem is that your database contains some content which would be introduced with beta 1 and 2.
Griffith breaks while upgrading your database.
Two options:

• use a backup of your database
• send me your database file and I will try to fix it manually
• fix it manually by yourself

Michael

[colo]

Thanks.

Have PM'd you the link to my database file.

Colo