Repository navigation
v1.1.0
The applications table uses a composite primary key (application_id, guild_id, source), meaning the same application_id can legitimately appear in multiple rows (once per guild/source combination).
The forwardings table originally had a foreign key on application_id alone, referencing only the application_id column of applications. SQLite reject this because a foreign key must reference a complete primary key or unique constraint. Since application_id by itself is not unique in applications, the constraint was invalid and caused a schema error when performing operations.
Fix applied
Removed the foreign key constraint from forwardings.application_id.
Deletes of applications now require manual cascading (or triggers) to clean up related rows in forwardings (and votes).
Since the database schema was changed this is a major update.
Related commits: