Skip to main content
This page demonstrates real-world filtering scenarios using the oper parameter and relation filtering capabilities.

​
Overview

The Rest Generic Class package provides powerful filtering through the oper parameter, supporting:
  • Simple equality and comparison operators
  • Complex AND/OR logic trees
  • Relation-based filtering
  • Date range queries
  • Full-text search patterns

​
Scenario 1: Basic Product Catalog Filter

Goal: Show active products in stock within a price range. 
GET /api/v1/products?select=["id","name","price","stock"]&relations=["category:id,name"]
Content-Type: application/json

{
  "oper": {
    "and": [
      "status|=|active",
      "price|>=|50",
      "price|<=|200",
      "stock|>|0"
    ]
  },
  "orderby": [{"price": "asc"}],
  "pagination": {"page": 1, "pageSize": 20}
}

​
Scenario 2: Search by Name with Category Filter

Goal: Search for “keyboard” products in the Electronics category. 
{
  "oper": {
    "and": [
      "name|like|%keyboard%",
      "status|=|active"
    ],
    "category": {
      "and": [
        "name|=|Electronics"
      ]
    }
  },
  "relations": ["category:id,name,slug"]
}
The like operator uses SQL LIKE syntax. Use % as a wildcard for partial matches. For case-insensitive searches, your database collation determines behavior.

​
Scenario 3: Complex OR Logic - Clearance or New Arrivals

Goal: Show products that are either on clearance (low stock) or newly added. 
{
  "oper": {
    "or": [
      {
        "and": [
          "stock|<=|10",
          "stock|>|0",
          "status|=|active"
        ]
      },
      {
        "and": [
          "created_at|>=|2024-03-01",
          "status|=|active"
        ]
      }
    ]
  },
  "orderby": [{"created_at": "desc"}]
}

​
Scenario 4: Multi-Category Filter

Goal: Show products from multiple categories using IN operator. 
{
  "oper": {
    "and": [
      "status|=|active",
      "category_id|in|3,5,7,9"
    ]
  },
  "relations": ["category:id,name"]
}

​
Date Range Queries

​
Scenario 5: Products Created This Month

Goal: List all products added in the current month. 
{
  "oper": {
    "and": [
      "created_at|>=|2024-03-01",
      "created_at|<|2024-04-01",
      "status|=|active"
    ]
  },
  "orderby": [{"created_at": "desc"}]
}

​
Scenario 6: Recently Updated Products

Goal: Find products updated in the last 7 days. 
{
  "oper": {
    "and": [
      "updated_at|>=|2024-03-08",
      "status|=|active"
    ]
  },
  "select": ["id", "name", "price", "updated_at"],
  "orderby": [{"updated_at": "desc"}]
}

​
Scenario 7: Seasonal Product Filter

Goal: Show products relevant to a specific season with date-based logic. 
{
  "oper": {
    "and": [
      "status|=|active",
      {
        "or": [
          "season|=|all-year",
          "season|=|winter"
        ]
      }
    ]
  }
}

​
Relation-Based Filtering

​
Scenario 8: Filter by Nested Relation

Goal: Find products with highly-rated reviews (rating >= 4). 
{
  "oper": {
    "and": ["status|=|active"],
    "reviews": {
      "and": ["rating|>=|4"]
    }
  },
  "relations": ["reviews:id,rating,comment,created_at"],
  "_nested": true
}
Set _nested: true to apply relation filters to both the query and the eager-loaded relations. Without this flag, relation filters only affect the main query (existence check).

​
Scenario 9: Filter by Category and Subcategory

Goal: Show products from Electronics category where subcategory is “Accessories”. 
{
  "oper": {
    "and": ["status|=|active"],
    "category": {
      "and": [
        "parent_category|=|Electronics",
        "name|=|Accessories"
      ]
    }
  },
  "relations": ["category:id,name,parent_category"]
}

​
Scenario 10: Products with Tags

Goal: Find products tagged with specific keywords (many-to-many relation). 
{
  "oper": {
    "and": ["status|=|active"],
    "tags": {
      "and": [
        "name|in|wireless,bluetooth,portable"
      ]
    }
  },
  "relations": ["tags:id,name"]
}

​
Multi-Condition Complex Filters

​
Scenario 11: Advanced Search with All Features

Goal: Comprehensive search combining text, price, date, stock, and relations. 
{
  "oper": {
    "and": [
      "name|like|%gaming%",
      "status|=|active",
      "price|>=|50",
      "price|<=|500",
      "stock|>|5",
      "created_at|>=|2024-01-01"
    ],
    "category": {
      "and": [
        "name|in|Electronics,Gaming,Computers"
      ]
    },
    "reviews": {
      "and": [
        "rating|>=|3.5"
      ]
    }
  },
  "relations": [
    "category:id,name",
    "reviews:id,rating"
  ],
  "select": [
    "id",
    "name",
    "price",
    "stock",
    "created_at"
  ],
  "orderby": [
    {"price": "asc"}
  ],
  "pagination": {
    "page": 1,
    "pageSize": 25
  }
}

​
Scenario 12: Exclude Specific Items

Goal: Show all products except specific excluded IDs and categories. 
{
  "oper": {
    "and": [
      "id|not in|5,12,18,24",
      "category_id|not in|99",
      "status|=|active"
    ]
  }
}

​
Scenario 13: Null/Not Null Checks

Goal: Find products with or without a description. 
{
  "oper": {
    "and": [
      "description|is not|null",
      "status|=|active"
    ]
  }
}

​
Performance Optimization Tips

1

Use Select to Limit Columns

Only fetch the columns you need:
{
  "select": ["id", "name", "price"],
  "relations": ["category:id,name"]
}
2

Add Database Indexes

Index frequently filtered columns:
$table->index(['status', 'price']);
$table->index(['created_at']);
$table->index(['category_id', 'status']);
3

Enable Caching for Repeated Queries

REST_CACHE_ENABLED=true
REST_CACHE_STORE=redis
REST_CACHE_TTL=300
4

Limit Relation Depth

Avoid loading too many nested relations:
{
  "relations": ["category:id,name"],
  "_nested": false
}

​
Supported Operators

OperatorExampleDescription
=status|=|activeExact match
!=status|!=|inactiveNot equal
>price|>|100Greater than
>=price|>=|100Greater or equal
<stock|<|10Less than
<=stock|<=|10Less or equal
likename|like|%keyboard%Pattern match
not likename|not like|%test%Pattern exclusion
inid|in|1,2,3In list
not inid|not in|5,6Not in list
isdeleted_at|is|nullNull check
is notdeleted_at|is not|nullNot null check
betweenprice|between|50,100Range (inclusive)
All operators are validated against the package’s allowlist. Custom operators can be added via configuration if needed.

​
Common Mistakes

Forgetting to add relations to RELATIONS constant
// In your model
const RELATIONS = ['category', 'reviews', 'tags'];
Unlisted relations will return a 400 error.
Exceeding filter limitsThe package enforces filtering.max_conditions (default: 100) to prevent database overload. Split large filters into multiple requests.
Invalid operator syntaxUse pipe separators: field|operator|value❌ Wrong: "price > 100"✅ Correct: "price|>|100"

​
Next Steps

Build docs developers (and LLMs) love

Get started for freeTalk to us