Part of elisa.plugins.database.database_updater View In Hierarchy
Known subclasses: elisa.plugins.database.tests.test_database_updater.DbUpNGDummy
DatabaseUpdaterClassic
will be used| Line # | Kind | Name | Docs |
|---|---|---|---|
| 330 | Method | __init__ | Undocumented |
| 333 | Method | get_user_version | Undocumented |
| 336 | Method | get_schema_version | Undocumented |
| 375 | Method | update_from | Undocumented |
| 385 | Method | create_schema | Undocumented |
| 397 | Method | do_conditional_updates | Undocumented |
| 433 | Method | update_db | Undocumented |
| 339 | Method | _update_done | Undocumented |
| 343 | Method | _get_pragma_version | Undocumented |
| 355 | Method | _schema_version_check | Undocumented |
| 371 | Method | _run_classic | Undocumented |
| 464 | Method | _upgrade_to_2 | This method updates the database user version to number two. The new |
| 477 | Method | _upgrade_to_3 | Upgrades the database to version 3. The new tables are movies, |
| 554 | Method | _upgrade_to_4 | Upgrades the database to version 4. TV Episodes poster uris |
| 583 | Method | _upgrade_to_5 | Upgrade the database to version 5. |
http://images.thetvdb.com/banners/episodes/79349-310842.jpg
to:
http://images.thetvdb.com/banners/episodes/79349/310842.jpg
Remove all the deletion triggers, replaced by explicit deletion code in the database parser. This is because using triggers in the DB, Storm was not aware of objects being deleted and was therefore quite confused. See https://bugs.launchpad.net/elisa/+bug/322700.