Have been seeing these values being added and removed from queries in SA randomly since updating to version 6 (or probably even in 5).
What is this? And why does Wappler keep adding and removing these randomly on random queries. In some queries it does not add these at all. Have seen this on all projects.
Good question, noticedt he saem
RECID (for as I can tell) stands for RECord ID. I am probably wrong, but still 
I believe recid refers to the uniquely identity a record in the database.
By default system uses recid as primary index in the absence of a defined index, so if query optimizer didn’t find any index to use it will use recId as a fallback value.
Probably always there, just not sure why it is getting exposed in the query results.
In some context it can also be a pointer to the FIRST record in a query result.
Bump.
Bump. Can someone please explain/fix this? @patrick/@George
It wastes so much time going through these lines as changes in code-diff!
Still awaiting a response. Bump.
this is a Wappler internal artifact, not related to any of your records.
So it can be safely ignored.
We have been doing so. But its a huge annoyance in code-diff and code review. Git shows numerous changes in a SA, when all we would have done is enabled output in one of the steps.
Wappler randomly adds and removes this value from queries. We have seen this irrespective of which version of Wappler we are on, ever since this started.
Please fix this to be consistent for all types of queries - or better yet, just remove this.
Will see if we can clean it up.
It will be helpful if you can indicate exactly when it is added.
We haven't been able to reproduce the adding and removing of this.
Usually, when we make changes in some other parts of a SA or the query itself, this shows up. But sometimes, it gets removed.
I was hoping to get some info about it with this post so I could understand why this is happening.. or if there is some way to disable it.
