Skip to content

Bugfix - Database Triggers

Compare
Choose a tag to compare
@DnOberon DnOberon released this 04 Jan 19:40
· 2237 commits to master since this release

Deep Lynx was using a sophisticated database trigger for managing node and edge insertion. These triggers allowed the automatic setting of a deleted_at field whenever someone entered a record with an existing id. Unfortunately, this method proved to be extremely time consuming on the database side and caused numerous slowdowns on even the small tables.

This release removed those triggers and replaced them with different functions and functionality. We still have point in time versioning, and we will still be able to support point in time querying - but the deleted_at field will no longer be as important when viewing the data. That field now indicates manual or automatic deletion of records not relating to initial data ingestion.