Managing database reference data and associated code

Question

Reference data or lookup tables are things like CustomerType, ProductType, etc. They change infrequently, occasionally a new type is added or the old resigned. In the code, they are often reproduced as enums / constants, and are also used to fill combo boxes. Adding a new type should not violate existing applications, and most often these new types are necessary only to support the functions of the new application, legacy applications should ignore it.

This situation will be familiar in most online stores, after a few years / months it is messy, uncontrollable, and if the database and code fail, bad things happen.

How do others deal with this problem? What does the code / DB look like and how is it executed by the version?

Answer 1

Do you mean that identifiers and tags are hardcoded in the code and displayed in the lookup table in the database?

The approach we have taken is to read identifiers and labels of type "from" and use them to populate lists.

(Fortunately) I didn’t have to support different versions of the application, which should read different sets of values ​​from the same lookup table.

, . (, 1.5) 1.5 . , (, 2.1), .

, , .

Answer 2

, , , , . , , : ( ) . enum , ( , , ..).

, ; , " ", "", , . enum ; , , , SQL-. , "primaryColors()". ; .

public static Color valueOf(int key);

; .

if (selectedColor == Colors.RED) {
   .
   .
   .

}

, , : , , , - ..

, , , , .