The most common reason for customized macros in dbt-mysql is that typical databases have relation names with three parts whereas MySQL has only two. E.g., a fully-qualified table name in Postgres is database.schema.table versus database.table in MySQL. The missing part in MySQL is the information_schema "catalog".
DBMS
Fully-qualified relation name
Parts
Postgres
database.schema.table
3
MySQL
database.table
2
In this particular case, we were able to get rid of one of the customized macros 🎉
Checklist
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] ~I have updated the CHANGELOG.md with information about my change~
resolves #134
Description
The most common reason for customized macros in dbt-mysql is that typical databases have relation names with three parts whereas MySQL has only two. E.g., a fully-qualified table name in Postgres is
database.schema.tableversusdatabase.tablein MySQL. The missing part in MySQL is theinformation_schema"catalog".database.schema.tabledatabase.tableIn this particular case, we were able to get rid of one of the customized macros 🎉
Checklist
CHANGELOG.mdwith information about my change~