I ran into the issue that for sql statements like the following
CREATE TABLE `some_table` (
code VARCHAR(6)
);
-- migration file later on
UPDATE TABLE `some_table`
ADD name VARCHAR(80) DEFAULT(`code`);
generates incorrect dbml when generated from an sql dump. The resulting dbml will have double backticks around the word code, as follows:
name VARCHAR(80) DEFAULT(``code``)
This leads to tools following in the pipeline to error.