gistfile1.txt

loic84: (TODO: this nomenclature is confusing, can we invent something better) "lookup operator"?
13:57 akaariai: loic84: which part does it refer to in relatedfield__datefield__year__gt=2013?
13:57 loic84: __gt
13:57 akaariai: ok, sounds good
13:58 akaariai: the relatedfield__datefield__year__gt is lookup, relatedfield__datefield is fields part, year is what?
13:58 loic84: 2013 could be the "lookup value"
13:58 akaariai: loic84: yes
13:59 loic84: hum year...
14:00 loic84: maybe "year__gt" is the operator?
14:00 akaariai: loic84: ok, gt is final operator? (Implemented by Lookup class...)
14:01 akaariai: the year is "extracts parts" (there could be multiple)? Implemented by Extract class.
14:02 ticketbot has left IRC (Remote host closed the connection)
14:02 ticketbot has joined ([email protected])
14:02 loic84: brain overflow...
14:03 akaariai: loic84: I know :)
14:03 loic84: do we have any other fields than dates that have similar extracts?
14:03 jax has joined ([email protected])
14:04 akaariai: loic84: for example jsonfield could have user__address__street
14:04 flenter has joined ([email protected])
14:04 loic84: ok so it's like a field drill down
14:05 akaariai: loic84: yes, or field transforming, for example sometextfield__as_int
14:05 akaariai: which does CAST(field as INT) in the query
14:06 loic84: maybe "modifier" is something we can exploit?
14:07 akaariai: loic84: seems good to me. Probably a good idea to rename the Extract class to Modifier class, too, then.
14:07 akaariai: And maybe Lookup class to Operator class?
14:07 loic84: we should save this for Tim, I'm sure he'll have spot on vocabulary for that.
14:08 akaariai: loic84: agreed
14:08 loic84: sounds good, or maybe prefix them with Lookup, i.e. LookupModifier and LookupOperator?
14:08 akaariai: loic84: sounds good