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.
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.
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.
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.
Bump. This random recid is still a huge problem when reviewing code in Git. There are numerous changes because Wappler adds and removes this value randomly from any SA query the team touches.
It will add this recid to a query when someone makes a change, and then removes it again RANDOMLY when query is updated again in future.
I'm resaving queries and the server action it's in because we changed a column name.
There are no other changes in this file, I haven't worked in it for a long time.
I'm expecting these changes:
Any update on this @George ?
There is a new key that shows up in the Beta version now: "collapsed". This is also not clear on what its function is and why does it get added.