Code

Changes between Version 12 and Version 13 of NoSqlSupport


Ignore:
Timestamp:
04/27/11 00:31:07 (3 years ago)
Author:
wkornewald
Comment:

removed query refactoring section

Legend:

Unmodified
Added
Removed
Modified
  • NoSqlSupport

    v12 v13  
    5353 
    5454Django-nonrel merely provides a `connection.feature.supports_select_related` flag which tells `QuerySet` that the backend won't return additional data for the related data in the result rows (otherwise `select_related()` causes bad results full of `None` values). All NoSQL backends set this flag to `False`. 
    55  
    56 = Query refactoring = 
    57  
    58 The following is non-critical in that even without the changes it's possible to write NoSQL backends. It's mentioned here in case the Django teams wants to clean the ORM up before adding NoSQL support. 
    59  
    60 Currently, `sql.Query` stores data in a format that is too SQL-specific. This is not a show-stopper. It's possible to read the data and handle it somehow. It's just not very convenient. The data should be stored in a more abstract way, probably like Alex Gaynor originally suggested for his Google Summer of Code project. 
    61  
    62 For example, JOIN aliases can be simple integers. There's also no need for all of the JOIN-related data structures. Also, instead of storing table and column names it's easier to deal with higher-level information like models and fields in these structures. 
    63  
    64 Another example is the way aggregates are represented. The data structures rely too heavily on SQL. 
    6555 
    6656= !AutoField =