Opened 16 years ago
Closed 16 years ago
#12739 closed (invalid)
Inconsistent sorting behavior in mult-table inheritance query for different database backends
| Reported by: | George Song | Owned by: | nobody | 
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.1 | 
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no | 
| Needs tests: | no | Patch needs improvement: | no | 
| Easy pickings: | no | UI/UX: | no | 
Description
Given the following models:
from django.db import models class A(models.Model): name = models.CharField(max_length=50) class B(A): pass class C(A): pass
The following query returns different queryset order for sqlite3 vs. postgresql_psycopg2:
A.objects.order_by('b', 'name')
SQLite will sort B objects, followed by C objects. PostgreSQL will sort C objects, followed by B objects.
  Note:
 See   TracTickets
 for help on using tickets.
    
This looks to be a DB level inconsistency, not something Django can control. Unless there's something I'm missing closing as wontfix.