[Core] Spaces in dbt model names for v1.8 upgrade guide

[dbeatty10]

Link to the page(s) on docs.getdbt.com requiring updates

Upgrade guide for v1.8:
https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-v1.8

Tell us more about this update

Neither of these bullet points tell the whole story, so I'd suggest amending or removing the following:

Spaces in dbt model names

We will begin deprecating support for spaces in dbt model names in v1.8 (raising a warning) before removing support entirely in v1.9 (raising an error). Reasons for removing spaces in model names include:

• Spaces in a model name make it impossible to --select the model name because the argument gets split into pieces over spaces very early in the pipeline.
• Most warehouses do not accept a table, or other object, with a space in its name.

Here's some more nuanced explanation:

1. Use a * wildcard to select a model name with a space

$ dbt list -s "my*model"
20:13:53  Running with dbt=1.7.10
20:13:53  Registered adapter: postgres=1.7.10
20:13:53  Found 1 model, 0 sources, 0 exposures, 0 metrics, 401 macros, 0 groups, 0 semantic models
my_project.my model

2. Many data platforms allow table names to contain spaces

The SQL standard describes quoted identifiers, and most popular databases support them (including allowing spaces). In fact, we have identifier quoting on by default for most adapters (dbt-snowflake being the notable exception).

Reviewers/Stakeholders/SMEs

.

Related GitHub issues

See #5347 and all associated issues.

• [CT-3564] for deprecation - we should not support spaces in model names dbt-core#9397
• Begin warning people about spaces in model names dbt-core#9886
• [Core] We won't support spaces in model names #5275
• Deprecating support for spaces #5295
• [Core] Upgrade guide for model names that contain spaces #5347
• Upgrade instructions for model names that contain spaces #5351

Additional information

No response