Closed GoogleCodeExporter closed 9 years ago
I've fixed the issue which was causing the crash when deleting tables
containing foreign keys.
Given that we've got a warning when the user saves the updated version of the
database, and we don't have a warning when deleting other tables containing
data, is there a specific reason for doing so on tables that have foreign keys?
Original comment by marxjohn...@gmail.com
on 5 Feb 2015 at 2:31
Just to clarify that, we have a confirmation dialog when any table is deleted
already, but are you saying we should have an additional one when a table
containing foreign keys is deleted?
Original comment by marxjohn...@gmail.com
on 5 Feb 2015 at 2:36
Hmm. probably not. Not sure why I made a fuss about this issue. 1 confirmation
dialogue should be enough.
Original comment by jajwil...@gmail.com
on 5 Feb 2015 at 2:43
Original issue reported on code.google.com by
jajwil...@gmail.com
on 12 Dec 2014 at 2:11