in_query doesn't consider limit of subquery.

[crayment]

The following will ignore the 1000 limit on the post_query:

comments = Parse::Query.new("Comment").tap do |comments_query|
  comments_query.in_query("post", Parse::Query.new("Post").tap do |posts_query|
    posts_query.eq('category', 'ruby')
    posts_query.limit = 1000
  end)
end.get

[adelevie]

Is the request somehow being malformed or this a parse idiosyncrasy?

On Mar 6, 2014, at 2:08 AM, Cody Rayment notifications@github.com wrote:

The following will ignore the 1000 limit on the post_query:

comments = Parse::Query.new("Comment").tap do |comments_query|
comments_query.in_query("post", Parse::Query.new("Post").tap do |posts_query|
post_query.eq('category', 'ruby')
posts_query.limit = 1000
end)
end.get
—
Reply to this email directly or view it on GitHub.

[crayment]

in_query seems to just not consider [:count, :limit, :skip, :include]:

query_hash = {Parse::Protocol::KEY_CLASS_NAME => query.class_name, "where" => query.where}
add_constraint(field, "$inQuery" => query_hash)

vs get which merges them into the query:

query = { "where" => CGI.escape(where_as_json.to_json) }
set_order(query)
[:count, :limit, :skip, :include].each {|a| merge_attribute(a, query)}

Looks like it doesn't consider order either but not sure if that would ever be an issue.