Aw yeah @amy— thanks for taking the time to write this up!
As Amy noted, we’ve been playing around with a custom materialization to make the implementation of this easier. dbt, in its current form, assumes that one model will produce only one relation (table/view) in a warehouse, and we suspect that if we try to use one materialization to create both a view and a table, some weird things might end up breaking!
But we’re going to try it out at some point just to see what happens 