from the dbt slack: ```dbters: do you ever get the...
# announcements
from the dbt slack:
Copy code
dbters: do you ever get the request to have a materialization option for a table that drops the table after the pipeline finishes? I’ve used this pattern a lot in the past for performance reasons. You run a pipeline and instead of using ctes, sometimes you need either a materialized view or a temp table to keep performance of transformations humming along. (classic example is when cross joins are involved in a temp table creation, but you don’t want the table hanging around after you use it).