MattV
Yeah I figured that but that's very inefficient, I now have to pull down 100 records when I might only need 2.. Why is post time not a constraint?
In classic/LiQL the post time constraint ended up being very inefficient, and even inaccurate with larger date ranges. So, assuming this omission is intentional in GraphQL, I'd say it was likely omitted because of similar reasons.
I don't know the actual reason though; I'd have to confer with our internal dev teams to confirm the actual reason for post time not being a constraint.
