Account always included in retrieved schemas

[allisonletts]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. create new connection
2. retrieve objects
3. deselect all objects, select two that are not Account (or more, I imagine)
4. generate SQL
5. See that Account is included in the list of retrieved schemas

Expected behavior
The schemas of the selected objects are retrieved

Screenshots
Last Response:

Message Console:

Desktop (please complete the following information):

• OS: Windows Server 2019
• Target Database: MariaDB

Additional context
It's weird to me that the objects list in the response is right, but the schema list is wrong.

[allisonletts]

Update: running the create tables function attempted to insert the Account table. It was unsuccessful because I left "drop and recreate" unchecked.

[acrosman]

That is weird. I'll figure it out.

[allisonletts]

This may be from a release or two ago. If it's not reproduceable on your end, I can find the release I'm using. I will say I don't think I've seen this before.

[allisonletts]

I'm going to close this for now. Just installed the latest version from source and I'm not having a problem.

[allisonletts]

@acrosman OOOOOOOHHHHHHH
It happens if you do the describe and move on to the proposed schema and then change your mind and go back to org objects and uncheck.
I actually don't know how to start over and/or tell it to completely freshly create the schema without anything it had before.

[acrosman]

Needs to be considered when resolving #107 and #101.