Hi Jörg, Regarding your question about database version support: https://docs.djangoproject.com/en/4.0/ref/databases/ lists the supported versions. Granted not as support grid and you have to scroll to every database, but it is usually in the first paragraph.
If f-expressions are currently supported your implementation could fall back to a slower implementation if it encounters them? Cheers, Florian On Sunday, April 24, 2022 at 10:19:16 PM UTC+2 Jörg Breitbart wrote: > Hi there, > > I have recently tried to tackle the known performance issues of > bulk_update. For more context plz see the original thread: > https://code.djangoproject.com/ticket/31202 > > In another issue we kinda ended up at the same idea again for a > different reason (https://code.djangoproject.com/ticket/33647). > > My early attempt for a faster implementation: > https://github.com/netzkolchose/django-fast-update > > This impl has several drawbacks/restrictions which I'd like to discuss, > before wasting more time to get things more aligned with the ORM, esp > these aspects: > - missing f-expression support > - only support for recent db engines > > @f-expressions > This is not directly possible from a constant table (thats how postgres > calls tables created from VALUES(...)). At this point idk if > f-expressions is an actively used thing with bulk_update at all, or if > support for those would just penalize the update throughput for no good > reason. My impl above currently skips such a workaround. Would like to > hear some more opinions about that. > > @db engine support > Are there any strict db support promises made by django releases? I see > that some django versions have notes about certain db engines and > versions, but I cant find a "support grid" or an explicit doc for that. > If django does not officially restrict db versions, then the impl above > would need some sort of a fallback for unsupported db versions. > > Plz also tell me, if this all sounds too wild for getting considered > into django (tbh the db version dependencies bug me alot), then it > prolly is better kept in a 3rd party package. > > Regards, > jerch > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7f6e3d0b-1bf0-4c41-8877-f9a28913d2ccn%40googlegroups.com.
