Skip to content

Prevent creating multiple ApplicationSetting by forcing it to always have id=1

What does this MR do?

This approach prevents writing duplicates. We force that every new object created to have id set to 1 which is primary key for the table.

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?


cc @stanhu @nick.thomas @yorickpeterse

Merge request reports