Hello, I am noticing that whatever i put in Query.select, the returned data will always contain the following fields
"total": 1,
"rows": [
{
"$sequence": 34,
"$createdAt": "2026-01-08T11:02:11.330+00:00",
"$updatedAt": "2026-01-08T11:08:43.799+00:00",
"$permissions": [
"read(\"user:12345\")",
"update(\"user:12345\")",
"delete(\"user:12345\")"
],
"$databaseId": "my_db_id",
"$tableId": "my_table"
}
]
Beside the fact that I think that many of those fields are internal system details that should not be exposed unless explicitly requested, if in my Query.select I put for example only the $id field
Query.select(["$id"])
why should I have all of those fields as well? It's ok that returning them is the default behaviour, but if I have explicitly reqeusted specific fields, i expect just them and no more others.
Additional columns returned when Query.select is used
@Jake just want to confirm whether this is default behaviour or if it's something we need to look into
it is not ready yet, but i am close to reach an mvp (actually a little bit more than an mvp :-))
Recommended threads
- Query.search limitation
Since `string` is deprecated I used `varchar`, and now I cant use `Query.contains` , so I setup fulltext index and started using `Query.search` the issue is `Qu...
- Searching by attribute "name" requires a...
I have a table "products" with a few columns I'm trying to search by, but I get this error: ```json { "message": "Searching by attribute \"name\" requires a...
- Issue with usage
I have a weird problem, my project on appwrite was using avarage 5-10k reads a day, it was okay, but suddenly last 7 days, reads are about 60k a day, the code h...