You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Bug report
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:
select * from stripe.prices where attrs->>'lookup_key' = 'foo';
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
Additional context
Docker container version of Postgres: 15.1.1.41
The text was updated successfully, but these errors were encountered: