►
From YouTube: Database migrations for a single GitLab codebase
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Well,
that
works
consider
me
surprised
that
it
actually
works.
That
array
as
I
say:
yes,
I've
been
banging
my
head
against
some
of
the
database
immigration
stuff
for
the
single
codebase
project
and
there's
a
couple
of
issues
there,
so
that
the
general
idea
is
that
we
would
back
port
all
the
schema
changes
from
EE
to
seee
and
then
eventually
make
sure
that
they
both
have
the
same
schema
file.
A
A
B
A
Know
anyway,
I'll
continue
me
done
it.
In
other
words,
there
are
a
few
different
kind
of
migrations
and
this
330
of
them
basically
sort
of
overarching
stories
that
that's
too
much
to
verify.
Can
we
actually
run
those
safely?
Will
they
feel
or
not?
I
would
expect
that
about
you're,
not
gonna
feel
cusco
no
longer
exists
that
they
depend
on
the
tables
are
in
their
homes
in
their
etc.
So
the
idea
originally
had
in
mind
us.
We
create
this
back
for
might
request,
and
then
we
bought
these
immigrations
to
seee
and
somehow
disabled
them.
A
If
is
yeah,
some
are
disabled
them.
The
problems
there's
there.
Essentially,
what
we
want
to
do
is
for
existing
ee
installations.
Nothing
happens
because
they
changes
it
there
for
ee
installations.
On
a
previous
version,
we
want
to
make
sure
that
any
datum
occasions,
whatever
are
still
run,
because
we're
only
back
coding,
schema
changes
so,
in
other
words,
have
to
say
data
with
LDAP
and
in
E
we
change
some
format.
A
You
are
creates
from
11
9
till
10
and
if
elephant
and
includes
all
these
changes,
we
want
those
migration
sections
and
then
the
probably
say
in
C.
We
don't
want
any
of
these
migrations
to
run
and
we
do
want
the
back
for
migrations,
and
this
is
difficult
because
we
have
no
way
of
detecting.
Are
you
in
existing
installation
going
to
this
version?
Are
you
see
installation
and
if
they're,
all
in
a
development
environment,
you
are
basically,
in
instance,.
A
A
We
also
can't
remove
them,
because
that
means,
if
you,
if
we
do
that
and
say,
1110
you'd,
have
to
out
great
to
eleven
nine
first
and
then
eleven
ten,
and
we
normally
only
do
that
with
major
releases.
So
that
means
we
would
have
to
delayed
until
twelve
zero
cuz.
Then
we
can
say:
oh
a
12-0
will
just
remove
all
the
immigrations.
We
add
the
backboard
in
seee
now
we're
done
because
she
have
to
upgrade
to
eleven
ten
I
guess.
First
Yorick.
A
E
B
A
My
main
concern
there
is
like
hey:
if,
because
of
that
deadline,
I
felt
that
has
a
bit
uncertain
about
saying,
hey
view.
We
can
do
all
that,
except
this
one
thing
that
will
be
a
month
later
now
from
a
setting
aside.
Those
deadlines
for
a
moment
as
far
as
I
can
tell
that
is
the
easiest
solution,
because
the
alternatives
that
we
modify
330
migrations
where
we
basically
say
yeah.
A
A
Because
it
kinda
depends
where
you
upgrade
from
like,
if
you
upgrade
from
with
very
ancient,
am
I
saying
this
correctly:
there
might
not
actually
be
problems
or
I
think,
but
it's
like
what,
if
this
case,
where,
like
I'm,
not
really
sure
how
that's
gonna
go,
you
know
it
could
work
or
it
could
cause
problems.
But
what.
A
The
idea
here
would
be
we
take
this
back
for
my
creation
that
I've
been
working
on
right
now
that
time
saps
near
2019
blah
blah
blah.
The
idea
is,
if
we
put
that
very
far
in
the
past,
it
will
run
first.
So
what
you
could
do
is
it
will
create
everything
necessary.
Then
we
can
modify
these
EE,
my
creations
to
say,
hey,
if
that
my
creation
is
already
ran,
don't
do
anything
that.
A
A
Have
a
class
for
it,
you
think
we've
abused
it
in
few
places.
Already
too,
we
do
just
sort
of
similar
with
some
specs
where
they
test
certain
column.
So
we
show
a
if
the
version
is
greater
or
lower.
Then
don't
do
this,
something
like
that
cuz.
Otherwise
they
fail
the
issue
there,
though,
if
they
you'd
have
to
do
a
330
times
for
the
up
approach
and
that
probably
also
for
the
down
approach,
although
I'm
not
sure,
because
my
back
port,
my
creation
doesn't
actually
revert.
A
Anything
like
I
deliberately
didn't
include
routing,
because,
if
I
were
to
say
back
port
and
LDAP
table
from
E
to
see
II
and
then
in
this
machine,
when
it
gets
referred
to,
remove
that
a
pass,
Imai
creation
will
fill.
If
you
tried
that
that
one
might
try
to
remove
this
table
so
basically
a
sort
of
a
point
where.
A
So
with
all
of
that
and
mine,
if
me
thinking
more
like
okay,
maybe
12
to
0
is
a
point
where
you
say:
hey,
that's
where
we
do
it
cuz
that
sort
of
lets
a
milestone.
We
can
say
hey
once
you're
at
12
0.
You
can't
go
back,
which
I
think
is
a
bit
more
reasonable,
saying:
oh
hey!
If
you're
at
11
tendons
broken
sorry,
you
can't
go
back
to
11
9.
A
Don't
officially
say
that
I
think
it
would
be
more
reasonable
to
this
one
time
say:
hey,
because
we
are
doing
this.
If
you
upgraded
12
0
I
mean
technically,
you
can
actually
refer
to
the
previous
version.
It's
just
that
these
EE
tables
and
columns
will
continue
to
exist,
but
as
Franco
C
ignores
them,
and
when
you
rerun
the
my
creation
it
will
skip
whatever
is
already
done.
It's
just
basically
a
point
in
time.
We
have
to
say,
like
you
know,
keep
in
mind
blah
blah
blah
yeah
as.
D
A
A
A
D
Looking
at
the
current
stats
for
for
the
single
codebase
project,
we
have
a
lot
of
items
moved
from
eleven
ten
to
eleven
eleven,
which
was
correct
it
we
have
around
what
is
a
64.
This
is
eighty
four
issues
assigned
to
eleven
eleven
right
or
12.0.
We
only
have
six,
which
means
I
can
expect
those
80-something
issues
to
be
hashed
and
then
the
other
have
to
be
moved
for
12
to
zero.
So
I,
don't
think
it's
unexpected
to
say
that
12
to
zero
should
be
our
target
right
and
I
think
it.
D
D
Can
I
repeat
this
just
to
see
whatever
I
understand
correctly,
so
the
reason
why
we
are
talking
about
11,
11
and
12
to
0
is
because
the
easiest
solution
for
us
would
be
to
force
people
to
upgrade
to
11
11
first.
This
is
the
hard
stop
they
have
like.
They
need
to
jump
to
that.
They
cannot
jump
over
11
11
and
in
11
11.
You
would
include
what
exactly
you
would
include
this
migration,
no.
A
A
We
could
keep
a
few
more
migration,
but
basically
the
idea
behind
the
removal
of
those
Imai
creations
is
that
this
few
migrations
I
have
to
go
in
and
figure
out.
Okay.
How
can
we
make
these?
Basically,
no
ops
if
the
stuff
is
already
there,
so
I
think
for
more
recent
migrations
that
might
not
be
necessary.
A
So
there's
two
radios:
we
put
this
in
twelve
zero.
We
remove
all
East
Pacific
migrations,
except
those
from
the
last
release,
those
1050
migrations.
If
any,
we
make
sure
that
they
can
operate
if
whatever
the
trying
to
migrate
is
not
there
because
foresee
that
won't
be
there
yet
and
then
towards
the
end.
We
have
this
big
back
port
migration.
That
only
E
is
a
no
op
and
I'll
see,
you
will
add
all
the
missing
stuff.
A
Sort
of
option
two:
is
we
keep
more
than
one
word
with
one
release
worth
of
migrations:
I,
don't
think
it
has
any
practical
benefits
for
users
because
they
still
have
to
upgrade
to
1111
first
as
per
our
sort
of
our
creating
policies,
and
he
means
more
work
for
us
means
there's
more
my
Gerson's
to
go
through
and
work
for
wise.
Probably
what
you'd
have
to
do
is
merge
this
after
the
feature
freeze
of
11,
3
of
12
0
and
then
say
hey
after
the
7th.
A
That
cannot
be
any
e
migrations
anymore
because
they
will
be
removed
because
otherwise
sort
of
happens
is
we
do
their
own.
Like
the
ninth
I,
say:
hey,
you
know
we're
ready.
It's
like
our
craft
is
5
integrations
I
fixed
those,
and
it's
like
three
new
migration
I
keep
doing
that
a
bunch
of
times
that
way.
We
don't
have
to
port
these
330
340.
Maybe
at
that
time
migrations
to
ze,
we
don't
have
to
worry
about
making
sure
it
actually
work,
compatible.
Blah
blah
blah
and
ze
ancestors
will
still
have
the
exact
same
schema.
A
A
A
D
A
See
people
making
a
boy
like
oh
yeah,
that's
too
much
right
then
in
some
point
will
be
the
argument
how
they
phrase
it,
but
that's
essentially
what
it
comes
down
to
the
people
feel
uneasy.
Maybe
moving
that
many
more
creations
I
believe.
The
last
discussion
regarding
this
that
was
planned
for
trolls
here
was
to
delete
my
gracious
older
than
a
year.
I
believe.
A
D
D
A
B
D
D
C
A
D
God
knows
what
else
right
like
some
breakages
things
like
that
happen
and
there's
the
first
thing
that
they
do
to
restore
service
is
just
roll
back
to
the
pediatrician,
but
code
and
database,
and
they
have
a
known
working
situation.
So
if
keeping
one
month
or
one
version
worth
of
migrations
would
allow
us
to
more
easily
do
that,
we
should
consider
it
the.
A
A
Sooner
you
heard
the
pro
I,
don't
think
would
actually
make
a
difference,
because,
let's
say
you
run
omniverse
and
you
upgrade
from
eleven
eleven
to
twelve
zero.
You
find
out
hey
we.
You
know
we
want
to
go
back.
Well,
you
reduce,
you
would
install
the
old
package
which
has
all
of
these
Ultima
gray
shirts,
still
there
and
this
backcourt
machine.
You
don't
need
to
refer
it
because
they,
whatever
it
adds,
is
just
ignored
by
the
previous
version.
A
You
would
have
to
refer
to
code
wise
anyway,
because
you
would
go
from
its.
You
know
single
code
base
version,
in
other
words
the
back.
What
stuff
can
be
reverted?
No
problem,
you
can
run
it
like
a
million
times
and
it
will
just
skip
whatever
it's
done
and
because
the
previous
version
really
still
has
these
old
migrations.
You
still
have
those
so
I.
Think
of
earnings
thread.
Recruiting
process
is
not
affected
in
any
negative
way.
A
D
A
Fortunately,
all
cases
make
sure
case
this
column
already
exists.
Don't
do
it
so
forgetful,
don't
calm,
it
shouldn't
have
any
impact,
but
I
can
definitely
see
this
being
a
bit
of
a
big
migration
for
existing
C
installations,
death
or
at
least
a
clone
off.
It
somehow
will
probably
be
a
good
candidate
for
this,
because
it
has
some
data
and
I
don't
like
generate
fake
data.
Yeah.
B
A
A
A
A
A
A
A
What
I'm
thinking
of
the
moment
is
that
we
would
announce
is
all
did
call
back
and
call
whatever
and
then
maybe
we
write
a
script
that
just
goes
solo,
much
requests.
Let
me
check
if
they
add
my
creations,
then
check
hey
is
well
and
then
just
add
a
notice.
Okay,
you
know
after
June
7th,
this
is
no
longer
possible.
So
please
yeah
it's
a
good
question.
What
do
we
ask
people
to
do.
A
A
D
A
Check
how
many
Americas
there
are
that
be
specific
migrations
right.
If
there's
like
three
merch
requested
no
big
deal,
but
if
it's
like
200
created
in
the
last
week,
then
we
might
need
to
make
the
announcement
earlier
just
so,
people
can
sort
of
take
into
account
like
oh,
hey,
there's
gonna,
be
this
point
in
time
where
we
closed
or
basically.
D
Engineers,
it's
gonna,
be
it's
gonna,
be
all
of
the
above
plus
more
so
every
individual
team
call
will
have
to
like
be
like
this
will
have
to
be
added.
What
I
can
do
is,
if
you
like,
create
a
general
snippets
and
but
you
know,
for
information
I
can
go
to
each
manager
and
tell
them
this.
Is
your
responsibility
yeah
share
with
the
team,
so
it's
gonna
be
team.
Cole,
it's
going
to
be
general
development,
back-end
front-end
and
every
individual
team
go
like.
Oh.
A
So
in
our
everywhere,
we
have
to
check
a
human
request.
I
think
what
we
could
do
as
a
sort
of
soft,
yes
deadline,
whatever
you
like
to
call,
it
is,
if
there's
not
too
many
immersive
guests
with
immigrations
by
get
lab
and
police,
we
could
ask
those
we're
like
hey.
Please
include
this
already
in
C
e
with
the
appropriate
checks,
and
please
ask
us
for
help.
A
A
A
A
A
A
D
A
A
It
goes
in
one
year
and
end
the
call
and
it's
gone
yeah.
That's
why
I
recorded
me
to
record
a
call
if
I
got
dammit
I
can't
say
they
didn't
do
something.
No
I
know
it's
the
YouTube,
alright
yeah,
so
that's
I,
think
all
for
me.
Yeah
I
have
enough
to
do
continue,
basically
figure
out
how
to
do
this
yeah.