FEATURE: Easy opt-in for more useful schema name generation behavior.

[randypitcherii]

Describe the feature

Most dbt users would benefit from a change in the default dbt behavior around schema names

Current Behavior: dbt prepends your default schema to your schema override config (if any).

Desired Behavior: dbt uses just the default schema in development and CI jobs, but treats the defaults schema as a fallback in production.

Describe alternatives you've considered

The current best approach is to have users individually override the generate_schema_name macro themselves with this behavior.

See here for the example I personally use.

Additional context

I could see this being useful as a project.yml config that users could set to true to opt in to this behavior.

That would keep this from being a breaking change for folks that don't know or care about this while also removing the need for users to get into the macro overriding business 💼

Who will this benefit?

Users that deploy in both dev and production environments and don't like surprises.

Are you interested in contributing this feature?

YES! I'd build it all out if you just let me know how you'd like the opt in to work or any other design concerns you have ♥️