gistfile1.txt

thomaslang: hi okito, are you there?
[17:50] okito: hey thomaslang
[17:51] thomaslang: I just pushed a new version of thomaslang/query -- reworked fetchRecords a little bit
[17:52] thomaslang: now it accepts this: s.findAll("name = 'b' OR count = %@",{wildCardValues:[2]})
[17:52] thomaslang: or this: s.findAll("name MATCHES %@",{wildCardValues:[/a/]})
[17:53] thomaslang: matching with regexps was added lately 
[17:53] thomaslang: s is your store
[17:53] okito: sweet
[17:53] okito: !
[17:54] thomaslang: some problems there are however
[17:54] thomaslang: right now you can't give a record type - resulting in looking at every record in the store to give the query result
[17:56] thomaslang: and i am not so sure if putting all this into a datasource is the right way
[17:56] okito: can't we use that as a filter condition
[17:56] martinmystere hat den Chatroom betreten.
[17:56] okito: well the DataSource really needs to make the decision about how to fullfill a request
[17:57] okito: but it should only need to return a Query object
[17:57] okito: and then let some other object take over from there
[17:58] thomaslang: i mean, isn't every developer supposed to write his/her own dataSource? how can we make this query functionallity generaly available if it is going into the dataSource?
[17:59] martinmystere: hi, I just joined the chan and only got the last 3 messages about the DataSource. Can someone pm me the whole conversation, I'd really like to read about what you guys say about the DataSource and requests with the server. Thanks.