Details for the issue

OK, another "but this is never going to happen in real life!!" case, but thought I'd mention it....
If you attach a database twice using different names* (who would do that?) and try to amend one of the tables in one of the attached databases, DB4S can't save the changes.

I guess you can't prevent it, but didn't know if the error could be 'sugared' somewhat for the user, so they had an inkling that they couldn't do what they're trying to do.

* For the avoidance of doubt, this was my schema.

a, b, and c are all the same attached database - just different names. The 'main' database is a different database (so I'm not attaching itself, if that makes sense...)

Useful extra information

I'm opening this issue because:

• DB4S is crashing
• DB4S has a bug
• DB4S needs a feature
• DB4S has another problem

I'm using DB4S on:

• Windows: ( version: ___ )
• Linux: ( distro: ___ )
• Mac OS: ( version: ___ )
• Other: ___

I'm using DB4S version:

• 3.10.99 (nightly from 12 Sep)
• 3.10.0-beta*
• 3.9.1
• Other: ___

I have also:

• Tried out the latest nightly version: https://github.com/sqlitebrowser/sqlitebrowser#nightly-builds
• Searched for an existing similar issue: https://github.com/sqlitebrowser/sqlitebrowser/issues?utf8=%E2%9C%93&q=is%3Aissue%20