GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Data tab: per-column filter row (query-by-example) that generates the WHERE filter · Issue #2648 · HeidiSQL/HeidiSQL

Data tab: per-column filter row (query-by-example) that generates the WHERE filter #2648

New issue
Copy link
New issue
Copy link
Open
Open
Data tab: per-column filter row (query-by-example) that generates the WHERE filter#2648
Copy link
Labels
featureA new feature to implementA new feature to implement

Description

@q2apro
q2apro
opened on Oct 30, 2026
Issue body actions

Is your feature request related to a problem? Please describe.
Finding rows by a known value in a known column takes too many steps in the Data tab. The current options:

  • Filter editor: type the WHERE clause by hand (column name, quoting, operator)
  • Multi-column filter: searches all columns with LIKE '%x%' – wrong hits, full scan, and it ignores the index on the column I actually mean
  • Quick filter: needs a cell with the wanted value already visible, or a right-click → prompt dialog

phpMyAdmin, DBeaver, DataGrip, TablePlus and Excel all offer a query-by-example form: one input per column, type a value, done. For the most common case ("show me the booking with boxid 12933335") HeidiSQL has no direct equivalent.

Describe the solution you'd like
An optional filter row directly above the grid header in the Data tab (toggle button next to "Filter", or a checkbox in the filter panel): one edit field per visible column.

  • Typing a value and pressing Enter generates the clause into the existing filter editor and applies it, e.g. boxid = 12933335
  • Operator derived from the column type and a few prefixes, same rules the Quick filter already uses: numeric/date → =, text → LIKE '%x%', !x → !=, >x / <x as typed, null / !null
  • Several filled fields are joined with AND
  • Clearing a field removes its clause; the generated text stays editable in the filter editor as today

This reuses the existing filter machinery and the Quick filter's clause generation, so it's mostly UI on top of what's already there.

Describe alternatives you've considered

  • Keeping the filter panel open and typing col = 'x' each time (works, but column names must be typed/autocompleted and quoting is on the user)
  • Quick filter via right-click → "column = [prompt]" (two clicks + dialog, and only for the column under the mouse)
  • The multi-column filter (unusable on tables where the value also occurs in other columns, and slow on big tables because every column gets a LIKE)

Additional context
HeidiSQL 12.22.0.7382 on Windows. This is the one phpMyAdmin feature I still miss after switching; everything else in the Data tab is faster in HeidiSQL.

Activity

  1. ansgarbecker
    added
    featureA new feature to implementA new feature to implement
    on Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA new feature to implementA new feature to implement

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.