Saved Filters

Save table filters for quick access to frequently used data views. Whether you’re using WHERE clauses or advanced column filters, saved filters let you instantly switch between different filtered views of your data.

Quick Start

  1. Apply a filter to your table data

    • Use the inline WHERE filter, or
    • Apply column filters using the grid’s filter menu

  2. Save the filter by clicking the save icon in the filters menu

  3. Name your filter - Give it a descriptive name like “Active Orders” or “Recent Customers”

  4. Reapply anytime - Click the filters menu and select your saved filter to instantly reapply it

Filter Types

Saved filters work with both filtering methods:

WHERE Clause Filters - Save complex SQL conditions that would be tedious to type repeatedly.

Column Filters - Save multi-column filtering and advanced grid configurations including sort order and grouping.

Managing Saved Filters

View Your Filters

Click the filters icon in the table toolbar to see all saved filters for the current table. Each filter shows the filter name with the filter conditions displayed underneath.

Rename a Filter

  1. Click the filters menu
  2. Click the edit icon next to the filter name
  3. Enter the new name
  4. Press Enter to save

Delete a Filter

  1. Click the filters menu
  2. Click the delete icon next to the filter
  3. Confirm deletion

Deleted filters are removed immediately and cannot be recovered.

How Filters Work

Filter Application

When you apply a saved filter:

  • WHERE filters: Rebuilds the SQL query with the saved WHERE clause
  • Column filters: Applies the saved filter model to the grid
  • Both filter types respect the current data state and work with other grid features

Filter Coexistence

WHERE filters and column filters can work together:

  • When a WHERE filter loads all matching rows, you can then apply column filters client-side
  • This provides powerful multi-layer filtering without additional server queries

Filter Storage

Saved filters are stored in VS Code settings (dbcode.table.filters) and sync automatically across devices via Settings Sync. Each filter is uniquely identified and associated with its specific table.

Use Cases

Common Scenarios

  • Development: Quickly switch between “Active Users”, “Test Data”, “Recent Changes”
  • Analysis: Save complex multi-column filters for recurring reports
  • Debugging: Store filters for error conditions, edge cases, or specific record sets
  • Data Review: Maintain filtered views for different review states or data quality checks

Best Practices

Descriptive Names: Use clear, specific names that describe what the filter shows (e.g., “Orders Last 30 Days” instead of “Filter 1”)

Organize by Purpose: Create filters that match your workflow - group related filters with prefixes like “DEV:”, “PROD:”, “QA:”

Regular Cleanup: Remove outdated filters to keep your list manageable and relevant

Test After Changes: If table schema changes, verify saved filters still work correctly

Limitations

  • Filters are table-specific and don’t transfer between different tables
  • Deleted tables don’t automatically clean up associated filters
  • Column filters depend on column names - renamed columns may break saved filters
  • Maximum of one WHERE filter and one column filter can be active simultaneously