Code

Changes between Version 14 and Version 15 of NonSqlBackends


Ignore:
Timestamp:
08/12/09 23:35:39 (5 years ago)
Author:
twanschik
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NonSqlBackends

    v14 v15  
    22 
    33Database query operations (get, count, ... entities) are provided to Django models via managers. Managers basically wrap around QuerySet methods. Internally Django's QuerySet class uses sql.Query whose default is sql.BaseQuery. sql.Query can be overridden to use a custom Query class (the backend). So we end up writting a Query class in order to provide a specific backend. So anything done in Django's Model methods or QuerySet methods which cannot be done for a specific backend should be moved into the Query in order to allow backends to specify what to do in such cases. 
     4Additionally the backends Query class should not be referenced by sql.Query (cause it can have nothing to do with sql) 
    45 
    56= sql.subqueries = 
     
    78The query classes defined in this module are used by QuerySet and Model, but it's not possible to override the subquery classes. 
    89 
    9 TODO: Is this necessary, at all? Probably yes if you want a clean port. 
     10TODO: Is this necessary, at all? Probably yes if you want a clean port so provide functionality to override subquery classes. 
    1011 
    1112= Fields =