Sam Barrow

Getting this too. Used to happen occasionally but would be fixed by a refresh. Lately though, it seems to permanently corrupt the database in question (can't open it ever again...

? I didn't mean it as a command... just thought it might help others. I'm using my own driver anyway.

Lol, no problem. I can't find an official source, just comments on the internet, but it does seem to be widely agreed on. Here's a similar issue on another project....

@koskimas Any thoughts on this? A simple flag when applying migrations for whether or not to use a locking connection would fix the problem. Not sure how easy that would...

>Based on some sources sqlite commits the transaction when it encounters certain DDL statements. I read that too but I think that might be for older versions only? But yes...

Just to make sure we're clear, I'm suggesting an optional flag that would just never be used with the other dialects because no one would ever need it. Only sqlite...

Yep.

Great, I'll test in the next few days.

> It's now possible in 0.17.1. I'll still leave this open. Maybe we could add a flag for `SqliteDialect` and `SqliteAdapter` for enabling transactions by default. Since sqlite has such...

I went ahead and did this but I realized there was another similar issue. The proxy is not marked as released until after a response is received to the release...