You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone. Sorry, my English is not good.
I have more than 200 database connections (SQL Server). Connection established successfully, no problems. Only when I look in SqlLab at the database selection, the database only displays 100 databases. Meanwhile, when I search for my other databases, it doesn't appear. Is it really the limit of 100? If I don't want a limit, where should I change the code? Thank you.
How to reproduce the bug
Screenshots/recordings
No response
Superset version
3.0.3
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
I have searched Superset docs and Slack and didn't find a solution to my problem.
I have searched the GitHub issue tracker and didn't find a similar bug report.
I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
The text was updated successfully, but these errors were encountered:
I had a similar issue with sqlite connectivity .
Establishing a connection, I am assuming won’t 100% guarantee that its actually linked to your DB. Check you connection path or even try sqlalchemy connection to define you absolute DB path.
Bug description
Hello everyone. Sorry, my English is not good.
I have more than 200 database connections (SQL Server). Connection established successfully, no problems. Only when I look in SqlLab at the database selection, the database only displays 100 databases. Meanwhile, when I search for my other databases, it doesn't appear. Is it really the limit of 100? If I don't want a limit, where should I change the code? Thank you.
How to reproduce the bug
Screenshots/recordings
No response
Superset version
3.0.3
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: