Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DATABASE SELECTOR at top of wateva window - GO-AROUND #3654

Open
DingBEN opened this issue Jan 31, 2020 · 0 comments
Open

DATABASE SELECTOR at top of wateva window - GO-AROUND #3654

DingBEN opened this issue Jan 31, 2020 · 0 comments

Comments

@DingBEN
Copy link

@DingBEN DingBEN commented Jan 31, 2020

Details

Sweet and short
The way around that pesky useless database selector that one must always chase
is to make sure all queries state the database: FROM database1.table
that way if the selector is on database2 ... it saves me the constant CLONK
...as mentioned in other posts, TRASH this approach, it is cumbersome and useless, only gets in the way
[ unless you implement it appwide... I now have trashed it, will never use it and will never worry about it, no more CLONKs ]

BASICALLY all your windows are tied to a query and its database
This amounts to changing your approach and make the app QUERYcentric(data) and let a list of queries be picked from a system table to move around. ...that also takes care of queries that address multiple databases. ...a 'current' database has not much meaning.

Operating system - WIN7 Pro

SQLiteStudio version - 3.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.