Context Navigation

Changes between Initial Version and Version 4 of Ticket #36030

-              initial
+              v4
 It leads to bugs, cuz at DB LVL,  INT / INT is also INT (2/3 = 0), and I doubt anyone who provides decimal there, excepts that behavior.
+=============
+I am using Postgres.
+{{{
+SomeModel.objects.create(some_field_of_type_int=2)
+sm = SomeModel.objects.annotate(x=F("some_field_of_type_int") / Decimal(3.0)).get()
+sm.x # returns 0
+}}}
+It will render Decimal of 3.0 to the query as 3 (INT). Because str(...) from Decimal(3.0) returns 3. (See cases at description)
+At python is not a problem, but at database it is, cus it breaks types. Calculation of two INTs at postgres, will return int as well, which is in this case 0, instead of 0.6666, which database would produce, if Django would render 3.0 instead of 3.
+Therefore, Django will return Decimal('0'), which I consider as Bug. This is not what anyone suppose to get.
+=============