Hannah R.

Hi! Admins will have visibility into org flights in our next release (targeted next week). In the meantime, we recommend using a service account or a centralized repo (example here)

Hi Noj! Thanks for the clarification, I'll flow the request back to our product team

Hi Alejandro! You can also use shares which are inherently read-only. You can read more about MotherDuck shares here

Hey folks, for those who missed the session earlier today, here is the recording

Hi folks! More to come on this.... very soon In the meantime, we recommend registering for the MD - DuckLake webinar on June 26. You can register here!

Hi Bob! We've configured this to avoid security risks where your device could be compromised or the local file might be inadvertently committed to a code repository. Is this behavior affecting your usage?

We use pg_duckdb to connect MotherDuck (and DuckDB) with applications that support Postgres but don't yet support DuckDB natively. Here's an example of how we integrate with dbt Cloud using pg_duckdb. dbt is a widely adopted solution and a priority for many of our users. SQLMesh is a newer entrant to the space, and we are interested in learning more about how MotherDuck users leverage SQLMesh. Let me know if you have any more questions about our ecosystem tools (or MotherDuck!).

Hi Vahe! Our team is following the dbt Fusion announcement. Currently, dbt Fusion doesn't have a timeline for Postgres support. Once Postgres is supported, we'll have a better idea of how we can leverage extensions we manage, like pg_duckdb, to take advantage of dbt Fusion.

Are you using either tool in your current workflows?