But see you just highlighted the problem I just described how SQL and JDBC are defined. Clearly MySQL is defined differently. You can argue all you want, that is the simple fact.

Really supporting MySQL needs some concept of "well MySQL uses these terms backwards, so we will need to invert the handling of them". You can "argue" all you want that @Table(name = "types", catalog = "config") is wrong for your setup (and you'd be absolutely correct based on SQL/JDBC!) but clearly that is the way MySQL is implemented.