View Ticket
Not logged in
Ticket UUID: 9ac7d2c07e05e36856976da3292815c629bdc3b1
Title: Problem with table designer within VS 2010
Status: Open Type: Feature_Request
Severity: Minor Priority: Low
Subsystem: VsDesigner Resolution: Workaround
Last Modified: 2012-12-29 06:14:16
Version Found In:
User Comments:
anonymous added on 2012-12-28 06:15:37:
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'

- 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.

mistachkin added on 2012-12-28 06:58:28: (text/x-fossil-plain)
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.

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

mistachkin (claiming to be anonymous) added on 2012-12-28 13:37:02: (text/x-fossil-plain)
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.

mistachkin added on 2012-12-29 06:14:16: (text/x-fossil-plain)
Changing to feature request.