filter operators

[Evertt]

Now you can make a filter like so:

let formatter = NSDateFormatter()
formatter.dateFormat = "dd-MM-yyyy"
let birthday = formatter.dateFromString("03-11-1990")!

let filter: Filter = ("name" == "Evert" && "age" > 18) || ("id" =~ 1...5 && "birthday" < birthday)

print(filter)

Which would print ((name = Evert and age > 18) or (id in [1, 2, 3, 4, 5] and birthday < 1990-11-03))

This is just to show you a work in progress. I didn't update any of the other code to work with this change. So in its current form Fluent would not compile.

I just wanted to ask you guys how you like it so far. So er.. how do you like it so far? ^_^

If you guys approve then I would like to continue to change the Query class so you can just do something like:

let users: [User] = Query().filter("age" > 18 && "subscribed" == true).orderBy("name", .asc).all()

[tanner0101]

I really like this addition. I'm close to merging a refactor to Fluent and we can add this to it afterward.

[Evertt]

Cool, happy to hear this work was not for nothing. @Joannis also suggested on Slack to add 3 more filters, namely .all([Filter]), .any([Filter]), and .none([Filter]). Because with .and and .either you can only add 2 filters at a time. And I agree, it's a nice addition. Of course there are no overloadable operators for those filters, but as was said in another thread, not everyone will be using the operators anyway.

[Evertt]

Or what we could also do is not add .all, .any and .none to Filter, but do add them as functions to Query, where Query would then translate them to filter using the .not, .both and .either cases.

[tanner0101]

Let's revisit #33. The query model has changed significantly since May.