I've been using parse on a project and was missing this functionality.
As a side note, I'm loving parse, but their iOS SDK is poorly designed. Like really badly designed. I had a few email exchanges with one of their devs, but it didn't really seem to go anywhere. You can't create subclasses of any of their objects because they like using static methods versus singleton instances. It's really stupid and it really ties you to using parse. You also have shit like this everywhere:
Helping subclassing to work more smoothly is definitely on our minds. A lot of people do subclass PFObject right now, and as you point out that means you need to handle queries in a slightly different way. It could be nicer, though, and we intend to make it nicer.
I've been using parse on a project and was missing this functionality.
As a side note, I'm loving parse, but their iOS SDK is poorly designed. Like really badly designed. I had a few email exchanges with one of their devs, but it didn't really seem to go anywhere. You can't create subclasses of any of their objects because they like using static methods versus singleton instances. It's really stupid and it really ties you to using parse. You also have shit like this everywhere:
Where this would be preferred: So you can create a wrapper/shim for PFObject, but that doesn't float across queries returning arrays of objects.And, yes, I considered writing my own wrapper around their REST API but I don't have that kind of time.