Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
0c18c703
Commit
0c18c703
authored
Jan 24, 2022
by
João Cunha
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix mermaid chart typo
parent
d43161f8
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/development/database/dbcheck-migrations-job.md
doc/development/database/dbcheck-migrations-job.md
+2
-2
No files found.
doc/development/database/dbcheck-migrations-job.md
View file @
0c18c703
...
@@ -51,14 +51,14 @@ graph LR
...
@@ -51,14 +51,14 @@ graph LR
1.
You checkout the
`dev`
working branch from the
`main`
target branch. At this point
1.
You checkout the
`dev`
working branch from the
`main`
target branch. At this point
each have their
`HEAD`
at commit A.
each have their
`HEAD`
at commit A.
1.
Someone works on the
`main`
branch and drops the
`
dependency_proxy_siz
e`
constraint, thus creating
1.
Someone works on the
`main`
branch and drops the
`
fk_rails_dbebdaa8f
e`
constraint, thus creating
commit B on
`main`
.
commit B on
`main`
.
1.
You add column
`dependency_proxy_size`
to your
`dev`
branch.
1.
You add column
`dependency_proxy_size`
to your
`dev`
branch.
1.
The
`db:check-migrations`
job fails for your
`dev`
branch's CI pipeline complaining that
1.
The
`db:check-migrations`
job fails for your
`dev`
branch's CI pipeline complaining that
the
`structure.sql`
file did not rollback to its expected state.
the
`structure.sql`
file did not rollback to its expected state.
This happened because
`dev`
had only commits A and C, not B. Thus, its database schema
This happened because
`dev`
had only commits A and C, not B. Thus, its database schema
did not know about the removal of the
`
dependency_proxy_siz
e`
constraint. So, when comparing the two
did not know about the removal of the
`
fk_rails_dbebdaa8f
e`
constraint. So, when comparing the two
schemas, the
`dev`
branch will have this constraint while the
`main`
branch won't.
schemas, the
`dev`
branch will have this constraint while the
`main`
branch won't.
This example really happened. See the
[
job failure logs
](
https://gitlab.com/gitlab-org/gitlab/-/jobs/1992050890
)
.
This example really happened. See the
[
job failure logs
](
https://gitlab.com/gitlab-org/gitlab/-/jobs/1992050890
)
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment