search

peeyush-tm / django-cube

Automatically exported from code.google.com/p/django-cube
GNU General Public License v3.0
1 stars 0 forks source link

take a design decision for django field lookup syntax in the constraints #8

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
for example 

c.constrain({'name__in': 'a_name'})

* should 'name__in' be considered as a dimension ? (in this case which syntax 
to use for coordinates ?)
* should 'name' be the dimension associated with 'name__in', and the sample 
space filtered with 'name__in' ? (which brings more complexity, and duplication 
with queryset.filter)

Original issue reported on code.google.com by seb...@gmail.com on 8 Jun 2010 at 12:20

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
'name__in' is considered as a dimension.
Syntax is Coords(name__in=[value1, value2])

Original comment by seb...@gmail.com on 10 Jun 2010 at 2:08