Open masinoa opened 11 years ago
FWIW, I agree that it would be better to have control over this situation.
@murphyke this is going to go away in a future release. The upcoming release candidate adds logging support and includes a warning about this behavior when it's triggered:
SqlBackend the createTable method blindly drops the table if it already exists. Is this what we want? It could instead throw an exception or the method could return some kind of status object, e.g. Completed, Failed(withReason), etc. Then the caller method can decide if the table should be dropped if it exists. Of course, we can also add a "dropIfExists" arg to the createTable method for convenience.