Low code platform for building business apps and workflows in minutes. Supports PostgreSQL, MySQL, MSSQL, MongoDB, Rest API, Docker, K8s, and more 🚀
A few weeks back @Ghrehh found an inconsistency with the view schemas (https://github.com/Budibase/budibase/pull/13625). Analysing the impact on this we realised we had some issues on the way we stored some view information, as some endpoints were trimming the non-visible columns completely while others were not.
After a discussion, we decided to never trim this information for different reasons. The main one is that the view schema might have other metadata rather than the visible/non-visible config, such as width, order, etc.
When retrieving a row from a view, we will trim out the non-visible fields, but we will never trim any info from the view itself.
mike12345567
commented
3 days ago
Description
A few weeks back @Ghrehh found an inconsistency with the view schemas (https://github.com/Budibase/budibase/pull/13625). Analysing the impact on this we realised we had some issues on the way we stored some view information, as some endpoints were trimming the non-visible columns completely while others were not.
After a discussion, we decided to never trim this information for different reasons. The main one is that the view schema might have other metadata rather than the visible/non-visible config, such as width, order, etc. When retrieving a row from a view, we will trim out the non-visible fields, but we will never trim any info from the view itself.
Related:
Addresses
Launchcontrol
Fixing some incoherences around view schemas