chore: Deprecate functions that should be replaced by migrations

[joc-a]

Description

Summary of the change: Deprecate functions that should be replaced by migrations

Detailed description:

• Why: These schema-altering functions will be replaced by migrations.
• How: Added WARNING deprecation level to the functions.

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update
• Other - deprecation

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

EXPOSED-101

[e5l]

lgtm

[williamboxhall]

@joc-a is the plan to eventually delete this function, or will it stay there just deprecated?

We find this method especially useful since we have an event-sourced system, and we use this to conveniently generate our non-source-of-truth projection tables. If something we to go wrong, we wouldn't be losing data, and could rebuild these projections easily. We'd love it if this method could stay in the API so that we don't need to bring in a migration system since it fits so well for our use case.

Thank you 🙏🏻

[e5l]

The schema util is going to stay with all functions inside. The message is here to indicate that this function doesn't generate a migration file, and you should avoid using it in production.