mirror of
https://github.com/Unleash/unleash.git
synced 2024-12-28 00:06:53 +01:00
51442a6cc4
We can just have a strategies column in the client_applications table. This solves all our needs, and thus avoids the need for an extra table. |
||
---|---|---|
.. | ||
001-initial-schema.down.sql | ||
001-initial-schema.up.sql | ||
002-add-description-to-features.down.sql | ||
002-add-description-to-features.up.sql | ||
003-add-parameters-template-to-strategies.down.sql | ||
003-add-parameters-template-to-strategies.up.sql | ||
004-insert-default-strategy-event.down.sql | ||
004-insert-default-strategy-event.up.sql | ||
004-insert-default-strategy.down.sql | ||
004-insert-default-strategy.up.sql | ||
005-archived-flag-to-features.down.sql | ||
005-archived-flag-to-features.up.sql | ||
006-rename-eventtype.down.sql | ||
006-rename-eventtype.up.sql | ||
007-add-strategies-to-features.down.sql | ||
007-add-strategies-to-features.up.sql | ||
008-create-metrics.down.sql | ||
008-create-metrics.up.sql | ||
010-create-client-instances.down.sql | ||
010-create-client-instances.up.sql |