#34956: Migration should not be allowed for a non-deterministic GeneratedField
-------------------------------------+-------------------------------------
Reporter: Sarah Boyce | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
* component: Uncategorized => Database layer (models, ORM)
* type: Uncategorized => Cleanup/optimization
Comment:
There are many functions that cannot be used of various databases, e.g.
`Random`, `SHA512`, `SHA384`, `SHA224`, `SHA1`, `MD5` cannot be used on
Oracle. As far as I'm, is not feasible for us to curate the list of
functions supported for each of database. This is also
[https://docs.djangoproject.com/en/dev/ref/models/fields/#generatedfield
documented] in `Database limitations`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34956#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018bae62b83f-c5eb6fc0-49fe-460e-8fd3-a5ba7b79888f-000000%40eu-central-1.amazonses.com.
