Marta Paes

(**CC:** @sjwiesman) Logging some [user feedback](https://materializeinc.slack.com/archives/C03648YB34N/p1660075107841369) about `dbt_utils.date_spine`: > as an aside, looks like the dbt_utils function could be better implemented with generate_series: > ```sql > materialize=> select generate_series(now(), now()...

Resurfacing the original discussion around `CREATE SOURCES`, for context: https://github.com/MaterializeInc/materialize/issues/5370#issuecomment-773569202. I'm +1 on sticking with `CREATE SOURCE` and creating multiple materialized views for the specified tables. The only thing I'd...

Ah, what a great discussion! I'd like to share our experience while building a prototype with the Orbit Model, which I think goes hand-in-hand with a lot of the changes...

Thanks for taking this on, @scherrca ! Are you done with the changes? I didn't go into too much detail in the ticket, but the idea behind changing the Documentation...

Thanks, @ruf-io! Also needs to be updated for [Cloud SQL](https://materialize.com/docs/integrations/gcp-cloud-sql/) and [Aurora](https://materialize.com/docs/integrations/aws-aurora/).

Linking this [💯 guide](https://materialize.notion.site/Postgres-SQL-w-Bastion-SSH-9c0bae3fe6214926bfc39f2fa69e885f) that should be replicated in the documentation.

Unsure whether this is something legit to expose, but AFAICT we don't make source or replica sizes available anywhere. How would one check the current size of a source, or...

Also +1 on dropping support for the inline syntax (as discussed in the thread Nicolle linked). I'm so excited about this separation of concerns! > This is in the path...

Huge +1, @mjibson.

@nrainer-materialize @def-, throwing this in the QA bucket so we can double-check if this is still an issue, or if we can close this out.