we want to implement business logic based on records in a table. We have two choices.
One way is to create an enum in code for each record in the table and in code compare the enum with the read record to decide what logic comes next. A drawback with this system is that if the key changes in the table(for example in autonumber fields), the application needs to be recompiled to reflect changes.
A second way to do this is to store variables in a configuration file for each record in the table, and in code compare the config variable with the read record to decide what logic comes next. A drwback with this system is that the config file could be manipulated and the application will stop working.
What is the best programming pattern for this matter?
Why not keep it all together and put a table in the database that tells you which business record table comes next?
Sorry, I can’t give a better answer. I need more info on what things your business logic is trying to do, and what orders these records can be in.