Changes between Version 1 and Version 2 of Ticket #29630, comment 7


Ignore:
Timestamp:
09/05/18 18:47:44 (4 years ago)
Author:
Simon Charette
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29630, comment 7

    v1 v2  
    33Any ORM bug does't fit into this category. The fact it only manifests itself on Oracle most of current contributors have limited knowledge of also makes it harder to resolve.
    44
    5 I've switched the component to the database layer because while it manifests itself in the admin in your case such an ambigously defined query can be trivially constructed by using `select_related('fk')` or `values('id', 'fk__id')`.
     5I've switched the component to the database layer because while it manifests itself in the admin in your case such an ambigously defined query can be trivially constructed by using `select_related('fk')[0:1]` or `values('id', 'fk__id')[0:1]`.
    66
    77@felixx are you aware of any changes that might caused such breakage? At this point I suspect some obscure flag Oracle flag might be interfering with native limit/offset support added in #28670 since the test suite passes against Oracle 12 on CI.
Back to Top