Skip to content

"No matching name" found when it clearly has been found #7231

@camsaul

Description

@camsaul

This is with 0.28.3

When I use the search widget for a User ID in a SQL query it tells me "No matching first name found":

screen shot 2018-03-28 at 4 13 56 pm

but when I hit enter the first name clearly was found because it shows up on the screen.

screen shot 2018-03-28 at 4 14 01 pm

Steps to repro:

  1. Connect the Metabase database (I'm using Postgres)
  2. Create new SQL question using this SQL:
    SELECT COUNT(*)
    FROM core_user
    WHERE {{user}}
  3. Wire up user param as Field Filter on core_user.id with Filter Widget Type of ID. No default value
  4. Try to use User search widget and type in the ID of a User
  5. "No First Name Found" pops up in widget
  6. Hit enter to choose ID
  7. First name shows up

Metadata

Metadata

Assignees

Labels

.Team/QueryingPriority:P1Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctnessQuerying/NativeThe SQL/native query editorQuerying/Parameters & VariablesFilter widgets, field filters, variables etc.Querying/RemappingRemapped display values, whether human-readable values or Field->Field remappingsType:BugProduct defects

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions