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
Is your feature request related to a problem? Please describe.
Yes, get an error coming from this packages, which not allowing me to connect and migrate to the Azure mysql db, so this feature is adding new rule to the migration that will solve this issue(django_rest_passwordreset.0002_pk_migration)
Describe the solution you'd like
To address the issue, you can modify this part of the code with the function (django_rest_passwordreset.0002_pk_migration) in migration to avoid removing primary key information directly. Instead, you can add a new 'key' field without the primary key constraint and then gradually transition to the new field. Here is an example modification:
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Darkbeast-glitch
changed the title
Compatibility with AZURE MySQL Server
Compatibility with production MYSQL Server
Jan 16, 2024
Is your feature request related to a problem? Please describe.
Yes, get an error coming from this packages, which not allowing me to connect and migrate to the Azure mysql db, so this feature is adding new rule to the migration that will solve this issue(django_rest_passwordreset.0002_pk_migration)
Describe the solution you'd like
To address the issue, you can modify this part of the code with the function (django_rest_passwordreset.0002_pk_migration) in migration to avoid removing primary key information directly. Instead, you can add a new 'key' field without the primary key constraint and then gradually transition to the new field. Here is an example modification:
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: