-
Notifications
You must be signed in to change notification settings - Fork 97
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
MSSQL issue after updating from 0.3 to 0.4 #93
Comments
Looks like mssql does not support select_for_update. Not sure how to solve this: the APScheduler events do not arrive in sequence and it is not unusual to receive a "submission" event after an "execution" event for the same job. Without the lock there would be a proliferation of |
...if it is just the If you can test the above and submit a PR that would be great - don't have mssql installed locally unfortunately. |
also noticed, while migrations, i have this error:
While creating db schema in the moment of migration 0.3 to 0.4, failed with removing name attribute from django_apscheduler_djangojob table. Also noticed that django_apscheduler_djangojob.Id in sql server is INT type and it is Autoincrement, and it can not save unique text as it is specified in model. |
Sorry I wasn't aware of those limitations when I made the changes. This probably is not very helpful, but it does not look like MSSQL is officially supported by Django. Perhaps a fork that can be supported by the MSSQL community would be appropriate? |
You mean fork from 0.3.0 version? |
I think v0.3.1 was the last version on which MSSQL sort of worked. If you did not experience any major issues on v0.3.1 it would be easiest to just keep using that version. If you have time / capacity / appetite you could also create a fork of v0.4.0 and try to retro-fit it for MSSQL yourself. Going forward, this project will probably only focus on supporting the DB backends that are also officially supported by Django. |
Thanks @jcass77 , i will fork v0.3.1 |
I have same issue. Updated Debian 9 to 10 for python 3.6 to 3.7.3 support. everything worked well before the Debian upgrade.
|
After upgrading to version 0.4, there is an issue with following trace:
I am using:
The text was updated successfully, but these errors were encountered: