Description

This action addresses a database schema design issue where many tables lack unique constraints (keys). This can lead to duplicate records being created when users submit forms multiple times, either intentionally or due to network issues causing retry behavior.

By adding appropriate unique constraints to the database schema, we can prevent duplicate records from being inserted and ensure data integrity across the system.

Problem

• Tables missing primary keys or unique constraints
• Repeated form submissions create multiple identical records
• No database-level protection against duplicates
• Data integrity issues during error scenarios or network retries

Solution

Add project based primary key to make sure record uniqueness.

• Actions
• Backlog
• Goals
• Ideas

Implement the existance check before inserting new record.

• Tasks