mongodb/mongoid · error · Mongoid::Errors::InvalidQuery

$gt argument cannot be a Range: #

Error message

$gt argument cannot be a Range: #{Errors::InvalidQuery.truncate_expr(condition)}

What it means

Raised by Mongoid::Matcher::Gt.matches? when the $gt condition is a Range. Ranges have ambiguous ordering semantics for greater-than comparison, so in-memory matching rejects them as the $gt predicate; the faulting input is the Range condition.

Solutions

  1. Use the range's upper bound as a scalar, e.g. { age: { '$gt' => 30 } } instead of a Range
  2. Combine $gte and $lt with $and for range-style queries
Defensive patterns

Strategy: type-guard

When it happens

Trigger: Thrown at lib/mongoid/matcher/gt.rb:21 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of mongodb/mongoid@0da0e23d71 (2026-08-23). Data as JSON: /api/errors/f24fd0bb3668255e. Report an issue: GitHub.

Appendix: source

Thrown at lib/mongoid/matcher/gt.rb:21

    # In-memory matcher for $gt expression.
    #
    # @see https://www.mongodb.com/docs/manual/reference/operator/query/gt/
    #
    # @api private
    module Gt
      # Returns whether a value satisfies a $gt expression.
      #
      # @param [ true | false ] exists Whether the value exists.
      # @param [ Object ] value The value to check.
      # @param [ Object ] condition The $gt condition predicate.
      #
      # @return [ true | false ] Whether the value matches.
      #
      # @api private
      module_function def matches?(exists, value, condition)
        case condition
        when Range
          raise Errors::InvalidQuery, "$gt argument cannot be a Range: #{Errors::InvalidQuery.truncate_expr(condition)}"
        end
        FieldOperator.apply_array_field_operator(exists, value, condition) do |v|
          FieldOperator.apply_comparison_operator(:>, v, condition)
        end
      end
    end
  end
end

View on GitHub (pinned to 0da0e23d71)