Add columns to dl_problem_priority?

[spike]

Hello.

I want to add additional fields onto problem that would effect how the priority is calculated. Should I add columns to dl_problem_priority to manage this, or should I create a whole new data lookup table?

Thoughts?

[HIROSHI SATOH]

Adding a Column to dl_problem_priority:

• Pros:
  • Simpler to implement if you only need to extend the existing functionality.
  • The new field will be tightly integrated with the existing priority calculation logic.
• Cons:
  • May complicate the table if too many additional fields are added.
  • Could lead to performance issues if the table grows too large or complex.

Creating a New Reference Table:

• Pros:
  • Provides more flexibility and scalability for more complex priority calculation logic.
  • Easier to manage and update without affecting the existing dl_problem_priority table.
• Cons:
  • Requires more initial setup and potentially more complex integration.
  • You will need to ensure the new table is referenced correctly in the priority calculation logic.

If the new field is closely related to existing priority calculations and won't introduce significant complexity, adding it to dl_problem_priority might be the best approach. However, if you anticipate needing more fields or more complex logic, creating a new reference table could offer better long-term flexibility.

[spike]

So ultimately, if we answer the question, we don't think there's a problem in adding columns to dl_problem_priority.

Thanks for your thoughts!