task_labels table updates are redundant for certain user behaviour

[melvinebenezer]

An update from the frontend /api/set_label updates the task_labels table (Postgres DB) in the backend. multiple clicks to report a messages creates that many entries in the DB

User reports one tag

User selects another tag and reports

The updates in the DB

Is this an acceptable behaviour ? Concern is while retrieving the flags from the DB after data collection. The SQL script writer should ensure that the most check flags are retrieved

Solution:

Update the labels for existing message_ids in text_labels table