System.Data.SQLite

Steps to reproduce:
- add a connection to a SQLite (password protected) database in the server explorer
- add a table (with an Id as primary key)
- save it
- try adding a second table
- add a foreign key to this table (which has no name at this moment)
- when saving the table and giving it a name a transaction not opened message is given
- after that, trying to refresh the tables list in the server explorer fails because 'database is locked'

Workaround:
- first close the table description (without saving it, then losing changes)
- close the connection in server explorer
- open connection in server explorer
- add the second table and save it with a name
- THEN add the constraint on the first table

Hope this helps.

The design-time components for Visual Studio are currently supported
on a very limited basis (i.e. they should continue to work as well as
they did in the legacy releases of System.Data.SQLite, e.g. 1.0.66.0).

However, if you would like to suggest a specific fix to this issue, I
would be happy to review it.

Suggested fix:
When opening the foreign key description, if the table has not been saved yet, ask the user to save it first thus giving it a name should prevent the bug from appearing.

Changing to feature request.