Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

where: {key: {_in: ["string"]}} results in _type "_text[]" does not exist

See original GitHub issue

After updating v1.0.0-beta.2 to v.1.0.0-beta.5 seemingly all GraphQL queries with _in-filters for text array columns started failing with error

{
  "errors": [
    {
      "extensions": {
        "path": "$",
        "code": "constraint-error"
      },
      "message": "type \"_text[]\" does not exist"
    }
  ]
}

I’m sorry that I don’t have more detailed report yet, nor I have manage to reproduce this from scratch.

Issue Analytics

State:
Created 4 years ago
Comments:5

Top GitHub Comments

1reaction

leoalvescommented, Aug 29, 2019

@datakurre,

v1.0.0.beta.3 had some breaking changes with _in queries. https://github.com/hasura/graphql-engine/releases/tag/v1.0.0-beta.3

If you can post your query and the variables your are using. I might be able to check if it is related to this change or not.

Cheers

0reactions

datakurrecommented, Aug 29, 2019

So, we were doing something unsupported and that worked just by accident. My current workaround is a custom operator allowing us to use where: {ids: {_eq: "id"}}. We could probably also use JSONB column instead of text[] to be able to use JSON operators.

Thanks a lot for help with this. Now I close this as “invalid”.

Top Results From Across the Web

Property 'includes' does not exist on type 'string[]'

Changing the compiler target to "es2016" in tsconfig.js should solve this issue.

Property does not exist on type String in TypeScript | bobbyhadz

The "Property does not exist on type String" error occurs when we try to access a property that does not exist on the...

SQL error messages and exceptions - Oracle Help Center

A RELEASE or ROLLBACK TO SAVEPOINT was specified, but the savepoint does not exist. Table 16. Class 40: Transaction Rollback. SQLSTATE, Message Text....

Documentation: 15: 43.5. Basic Statements - PostgreSQL

In this section and the following ones, we describe all the statement types that are explicitly understood by PL/pgSQL. Anything not recognized as...

13.1.20 CREATE TABLE Statement - MySQL :: Developer Zone

An error occurs if the table exists, if there is no default database, ... DEFAULT does not apply to the BLOB , TEXT...