-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
MSSQL Compatibility #2723
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
base: master
Are you sure you want to change the base?
MSSQL Compatibility #2723
Conversation
|
tests are failing due to the missing of database conneciton with MSSQL, knowing that it suppposed to configured with |
|
I silenced the warning in master, can you pull the latest changes? |
|
Thanks for the great work! I do not see any change to functionality, so what was the issue? |
to replicate the error: 1- Create a ModelView that connected to MSSQL Table includes more number of records to be paginated. |
|
But I cannot see where you fixed the issue. Sorry for being dense. |
|
i can't see this either 😄 , honestly this PR gone throught many branches and local merges until i forget what i've done , maybe the issue is just addressed throught all perviouse PRs. Anyway, we can just consider this PR as enabling the use of MSSQL with a very limited test cases. later on, i will modify the /tests/sqla ALL functions to be parametrized so that they should be tested againest (postgres, mssql , and sqllite) |
|
Is pymssql required? I do not see any import. |
Yes it is, SQLAlchmey impots it internally. without this PR MSSQL test won't pass since no container of MSSQL. this PR added container configuration for both devcontainer and github/workflow |
|
I would then convert/close this PR to parametrize the db fixture, since the additional test can removed. |
|
yes sure |
This PR address the issue that raises whenever the end user navigate to any page using MSSQL database. The MSSQL restricts using LIMIT and OFFSET without sorting,