-
Notifications
You must be signed in to change notification settings - Fork 145
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
Use db_default for auto-UUID fields in Django 5 #10958
Comments
Consider removing |
jacobtylerwalls
added a commit
that referenced
this issue
Nov 6, 2024
jacobtylerwalls
added a commit
that referenced
this issue
Nov 7, 2024
jacobtylerwalls
added a commit
that referenced
this issue
Nov 11, 2024
jacobtylerwalls
added a commit
that referenced
this issue
Dec 3, 2024
jacobtylerwalls
added a commit
that referenced
this issue
Dec 3, 2024
11 tasks
jacobtylerwalls
added a commit
that referenced
this issue
Feb 18, 2025
10 tasks
jacobtylerwalls
added a commit
that referenced
this issue
Feb 21, 2025
jacobtylerwalls
added a commit
that referenced
this issue
Feb 24, 2025
jacobtylerwalls
added a commit
that referenced
this issue
Feb 24, 2025
jacobtylerwalls
added a commit
that referenced
this issue
Feb 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Django 5 is the minimum required version, we can just use db_default for database-generated UUIDs and drop our custom implementation, which currently throws errors if you try to
manage.py sqlmigrate
:The text was updated successfully, but these errors were encountered: