Hi Jan, In my view, branches are primarily intended for isolating tests and later merging them back (commonly referred to as the WAP scenario). Tags, conversely, serve the purpose of marking significant snapshots for reproducibility or auditing.
Views essentially act as a shorthand for queries. Creating or replacing a view is a metadata operation with no data involvement. So, branching and tagging support may be an overkill. However, when dealing with materialized views, it becomes crucial to support branching and tagging, given that these operations involve data manipulation. Thanks, Ajantha
