quoting; ... so that when "PRAGMA legacy_alter_table" is set behaviour is still compatible with versions 3.24 and earlier).
WTH where would/should we set that PRAGMA? I think that would be in sqlalchemy's sqlite backend? Coreybc can you take over from here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in cinder package in Ubuntu: Triaged Status in nova package in Ubuntu: Triaged Status in sqlite3 package in Ubuntu: New Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
