Skip to content

warnings when searching stripe prices using the JSON attrs column #286

@vickkhera

Description

@vickkhera

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

A clear and concise description of what the bug is.

When searching for prices by the lookup_key field, a warning is emitted. The query still succeeds and returns the expected matching records.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Install the foreign table wrapper for stripe as per the documentation and create the stripe.prices foreign table.
  2. run this query in the psql CLI: select * from stripe.prices where attrs->>'lookup_key' = 'foo';
  3. see the warning
postgres=> select * from stripe.prices where attrs->>'lookup_key' = 'foo';
WARNING:  unsupported operator expression in qual: {OPEXPR :opno 98 :opfuncid 67 :opresulttype 16 :opretset false :opcollid 0 :inputcollid 100 :args ({OPEXPR :opno 3477 :opfuncid 3214 :opresulttype 25 :opretset false :opcollid 100 :inputcollid 100 :args ({VAR :varno 1 :varattno 8 :vartype 3802 :vartypmod -1 :varcollid 0 :varlevelsup 0 :varnosyn 1 :varattnosyn 8 :location 34} {CONST :consttype 25 :consttypmod -1 :constcollid 100 :constlen -1 :constbyval false :constisnull false :location 42 :constvalue 14 [ 56 0 0 0 108 111 111 107 117 112 95 107 101 121 ]}) :location 39} {CONST :consttype 25 :consttypmod -1 :constcollid 100 :constlen -1 :constbyval false :constisnull false :location 57 :constvalue 7 [ 28 0 0 0 102 111 111 ]}) :location 55}
DETAIL:  Wrappers
 id | active | currency | product | unit_amount | type | created | attrs
----+--------+----------+---------+-------------+------+---------+-------
(0 rows)

Similar error happens if I use LIKE instead of = and even when there are records that match.

Side note: it would be really awesome if we could promote additional fields like lookup_key to be columns rather than having to reference them via the JSONB column, but not a big deal.

Expected behavior

No warnings should be emitted.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

  • OS: macOS running local dev in docker
  • Browser (if applies) [e.g. chrome, safari] n/a
  • Version of supabase-js: [e.g. 6.0.2] @supabase/supabase-js@2.43.4
  • Version of Node.js: [e.g. 10.10.0] v22.2.0

Additional context

Docker container version of Postgres: 15.1.1.41

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions