Re-reading your reply, I think I've misunderstood your intent there (I didn't realise who the author was). Please disregard my previous reply.
On Sunday, 19 November 2017 09:59:44 UTC+11, Josh Smeaton wrote: > > Until you want to aggregate or filter on that calculation, and perform > that filtering in the database rather than pulling back millions of records > to do so in python. The database *must* be involved. > > On Sunday, 19 November 2017 06:32:48 UTC+11, [email protected] > wrote: >> >> Such computations always end up slightly different in some >>> edge cases >>> >> I agree. >> We can document this fact. Model authors should be aware that they are >> not allowed to use anything but literals. All other functions are used on >> their own risc. I believe that comparition of two integers or strings >> should work stable across all modern platforms. >> >> I still believe database shall not be involved in this process.I do not >> need database to compare two digits. >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/33fd5466-f790-4bdd-941e-80e81701e2af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
