migration

func Get202009171251 ¶

func Get202009171251() *migrate.Migration

func Get202010071530 ¶ added in v0.3.0

func Get202010071530() *migrate.Migration

func Get202010221010 ¶

func Get202010221010() *migrate.Migration

func Get202012041103 ¶ added in v0.3.0

func Get202012041103() *migrate.Migration

func Get202012091055 ¶ added in v0.3.0

func Get202012091055() *migrate.Migration

func Get2020121691335 ¶ added in v0.3.0

func Get2020121691335() *migrate.Migration

Get2020121691335 updates the primary key on events table.

Fixes: https://github.com/tinkerbell/tink/issues/379

We can have multiple events generated at a given time, therefore the value of 'created_at' field will be same for each event. This violates the unique constraint on "events_pkey", when these events are add to the events table.

The migration changes the primary key on events table from 'created_at' to `id`, which will always be unique for each event generated at any point in time.

func Get2021032610300 ¶ added in v0.6.0

func Get2021032610300() *migrate.Migration

Get202103261030 removes the event system tables and triggers.

Fixes: https://github.com/tinkerbell/tink/issues/464

The event system in place relies on triggers. It causes many problems because of its 8k characters limitation. CAPT is suffering from this limitation.

func GetMigrations ¶

func GetMigrations() *migrate.MemoryMigrationSource