don't ask if we want to drop empty tables
Bug #103923 reported by
brettatoms
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bauble |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
Don't ask to drop empty tables, just drop 'em. It's better that we drop and recreate them just in case the schema has changed.
| Changed in bauble: | |
| importance: | Undecided → Low |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| brettatoms (brettatoms) wrote | #1 |
To post a comment you must log in.
Beware that checking if a table is empty, i.e. len(select id from some_table), can cause the import to deadlock because the select could be waiting for the import to finish.
The problem seems to be when the table is in an inbetween state b/c it's been dropped in transaction as a dependency of another table so when we go to check if it has rows it seems like the database is waiting for the transaction to finish and....LOCK.