Commit 10629c69 authored by pbair's avatar pbair

Add link to issue about schema_migration versions

Add a comment in structure.sql that links to the announcement issue for
the changes to how schema_migration versions are handled.
parent fe433bd7
...@@ -22919,3 +22919,4 @@ ALTER TABLE public.product_analytics_events_experimental ...@@ -22919,3 +22919,4 @@ ALTER TABLE public.product_analytics_events_experimental
-- schema_migrations.version information is no longer stored in this file, -- schema_migrations.version information is no longer stored in this file,
-- but instead tracked in the db/schema_migrations directory -- but instead tracked in the db/schema_migrations directory
-- see https://gitlab.com/gitlab-org/gitlab/-/issues/218590 for details
...@@ -26,6 +26,7 @@ module Gitlab ...@@ -26,6 +26,7 @@ module Gitlab
io << <<~MSG io << <<~MSG
-- schema_migrations.version information is no longer stored in this file, -- schema_migrations.version information is no longer stored in this file,
-- but instead tracked in the db/schema_migrations directory -- but instead tracked in the db/schema_migrations directory
-- see https://gitlab.com/gitlab-org/gitlab/-/issues/218590 for details
MSG MSG
nil nil
......
...@@ -29,3 +29,4 @@ CREATE INDEX index_abuse_reports_on_user_id ON public.abuse_reports USING btree ...@@ -29,3 +29,4 @@ CREATE INDEX index_abuse_reports_on_user_id ON public.abuse_reports USING btree
-- schema_migrations.version information is no longer stored in this file, -- schema_migrations.version information is no longer stored in this file,
-- but instead tracked in the db/schema_migrations directory -- but instead tracked in the db/schema_migrations directory
-- see https://gitlab.com/gitlab-org/gitlab/-/issues/218590 for details
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment