Invalid query: Attribute not found in schema even though query, and attribute are correct/exist.

[green granite]

Hiya. I'm trying to use the REST API with documents and doing a simple select with query:

https://<mydomain>/v1/databases/<database>/collections/<collection>/documents?queries[]=%7B%22method%22%3A%22equal%22%2C%22column%22%3A%22uuid%22%2C%22values%22%3A%5B%22abcdefg%22%5D%7D

({"method":"equal","column":"uuid","values":["abcdefg"]})

and getting

    "message": "Invalid query: Attribute not found in schema: ",
    "code": 400,
    "type": "general_query_invalid",
    "version": "1.6.0",
    "file": "/usr/src/code/app/controllers/api/databases.php",
    "line": 3099,
    "trace": 

even though the attribute definitely does exist. Could this be an installation error on my part, perhaps? Thanks for the help

The fix was that I needed to write 'attribute' instead of 'column' in the query.

Or maybe I'm misunderstanding how to use the query argument. First time using it.

[sweet halo]

I can help with that this error usually happens when the field name in your query doesn’t exactly match the attribute name in your collection schema (case-sensitive) or if the document schema hasn’t been updated after adding the field.

Did you manually create the uuid field in the dashboard or through the API?

[sage marsh]

Your query should have "attribute":"uuid" instead of "column":"uuid"

[green granite]

I created it through the dashboard, so not sure if that would be an issue...

[green granite]

Ah! That's probably it. Will try later. I was a bit confused with the naming scheme in the query document. Why does it talk about table, row and column?

Is it to generalize the doc reference?

[sage marsh]

We recently changed terminology to be more in line with the technology being used (SQL databases), but queries have not been updated yet. Often people are using the SDKs, so won't see the encoded form

[green granite]

Solved!