Currently Naming is a dictionary. We need to make it a class with explicitly listed instance variables that are used in the mapping process. There is no reason to have it a dictionary besides historical convenience (aka laziness).
Note: At the time of writing this issue this can be done on the sql-annotations-unstable branch of 2.0, since some of the changes were already made.
While working on #430 I'm coming to conclusion that the Naming as an object should be removed and kept just as a dictionary with SettingValue values. Interpretation left to backends.
Currently
Naming
is a dictionary. We need to make it a class with explicitly listed instance variables that are used in the mapping process. There is no reason to have it a dictionary besides historical convenience (aka laziness).Note: At the time of writing this issue this can be done on the
sql-annotations-unstable
branch of2.0
, since some of the changes were already made.