This just blew my mind. Due to the fact that editing a column name, format, etc on a view changes the base table, I thought that adding a column to a view added them to the base table. But it doesn’t- it adds them to the view only, making the view a first class table in it’s own right.
I’m still getting my head around what this means. At a minimum, it means that you can uses views as a way of splitting up a large table into a bunch of 1:1 linked tables- one master and a bunch of small views.
I totally missed this fundamental aspect of notion- it’s not mentioned in the docs, and I guess I’m just kinda stupid
- Has anyone else missed this?
- If I wanted to refactor a table and move some columns into a view, but I already have a bunch of formulae and views etc using the existing column names, how would I go about this? I thought about creating a view showing the existing column I want to “move”, scripting copy the values across to a new view column using a button, deleting the old column and renaming the existing column. But this deletes the old column from everywhere I use it