c046094880
GORM has certain downsides: - Code-first approach, where queries have to be translated to the Go code required to execute them. - GORM comes with its own SQLite implementation, which doesn't provide an on-connect callback. This means that new connections cannot correctly enable foreign key constraints, causing database consistency issues. [SQLC](https://sqlc.dev/) solves these issues for us. This commit doesn't fully replace GORM with SQLC, but introduces it for a few queries. Once all queries have been converted, GORM can be removed completely.
16 lines
635 B
SQL
16 lines
635 B
SQL
-- Drop tables that were in use in beta versions of Flamenco. These might exist
|
|
-- in developer databases, as well as databases of studios following the `main`
|
|
-- branch, such as Blender Studio.
|
|
--
|
|
-- WARNING: this migration simply drops the tables. Their data is erased, and
|
|
-- cannot be brought back by rolling the migration back.
|
|
--
|
|
-- +goose Up
|
|
DROP INDEX IF EXISTS `idx_worker_clusters_uuid`;
|
|
DROP TABLE IF EXISTS `worker_cluster_membership`;
|
|
DROP TABLE IF EXISTS `worker_clusters`;
|
|
|
|
-- +goose Down
|
|
-- Do not recreate these tables, as no release of Flamenco ever used them.
|
|
-- Also their contents wouldn't be brought back anyway.
|