Changes between Version 15 and Version 16 of NoSqlSupport


Ignore:
Timestamp:
Apr 27, 2011, 3:20:02 AM (14 years ago)
Author:
Waldemar Kornewald
Comment:

minor issues belong at the bottom

Legend:

Unmodified
Added
Removed
Modified

  • NoSqlSupport

    v15 v16  
    1919
    2020Also take a look at the [http://djangopackages.com/grids/g/nosql/ feature comparison matrix] for an overview of what is supported and what is missing. Database-specific features are sometimes provided by an automatically added manager. For example, MongoDB adds a manager which adds map-reduce and other MongoDB-specific features.
    21 
    22 = Minor issues =
    23 
    24 The default ordering on permissions requires JOINs. This makes them unusable on NoSQL DBs.
    25 
    26 The permission creation code uses an `__in` lookup with too many values. App Engine can only handle 30 values (except for the primary key which can handle 500). This could be worked around, but the limitation was added for efficiency reasons (`__in` lookups are converted into a set of queries that are executed in parallel and then de-duplicated). Thus, it's not really a solution to just run multiple of those queries. Instead, the permission creation code should just fetch all permissions at once. Maybe in a later App Engine release this limitation will be removed when App Engine's new query mechanism goes live (which supports `OR` queries and gets rid of several other limitations).
    2721
    2822= Representing result rows =
    … …  
    144138
    145139Multi-table inheritance requires JOIN support, so this feature can't be fully supported. For convenience it would be nice to allow subclassing a non-abstract model, but only copying its fields as if it were abstract.
     140
     141
     142= Minor issues =
     143
     144The default ordering on permissions requires JOINs. This makes them unusable on NoSQL DBs.
     145
     146The permission creation code uses an `__in` lookup with too many values. App Engine can only handle 30 values (except for the primary key which can handle 500). This could be worked around, but the limitation was added for efficiency reasons (`__in` lookups are converted into a set of queries that are executed in parallel and then de-duplicated). Thus, it's not really a solution to just run multiple of those queries. Instead, the permission creation code should just fetch all permissions at once. Maybe in a later App Engine release this limitation will be removed when App Engine's new query mechanism goes live (which supports `OR` queries and gets rid of several other limitations).
Back to Top