Handle status table integrity properly

BitsDevelopmentTeam / bits-server

Presence and logging daemon for BITS system.

GNU General Public License v3.0

5 stars 2 forks source link

Open esseks opened 11 years ago

esseks commented 11 years ago

Currently, we perform a soft check to make sure that no two equal (close/close, open/open...) events are logged sequentially.

This should be moved to the DBMS layer using a proper CHECK constraint.

esseks commented 10 years ago

DB integrity checks via triggers are DBMS-dependent. I am still trying to find a proper way to do this.