►
From YouTube: 2022-05-25 Workspace weekly
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
B
A
B
B
It's
very
much
deserved,
so
I
have
no
doubts
about
it
like
I
want
to
ask
one
questions
very
friends,
and
I
need
to
imagine
that
the
rounds
back
feeling
is
done.
The
members
backfilling
is
in
on
the
way
like
it's
already
started.
A
Members
but
feeling
I
think
it's
merged
right.
Yes,
okay,
I
didn't
check
the
status
on
the
on
the
migration
to
be
totally
honest
with
you,
but
I
can
do
that
during
the
caller.
After
the
call.
B
A
Almost
so
database
changes
yeah.
There
are
a
couple
of
follow-ups,
at
least
from
from
the
routes
perspective.
We
need
to
do
some
cleanups,
remove
some
constraints,
add
some
constraints
and
so
on
so
get
the
database
side
in
order.
But
then
there
is
also
one
kind
of
bigish
migration
that
is
related
to
syncing
attributes.
A
So
we
had
that
issue
where
attributes
got
out
of
sync:
I'm
working
on
a
fix
it
in
it's
in
review,
hopefully,
should
be
merged
soon,
and
then
we
can
kind
of
monitor
and
see.
If
that
really
fixes
the
thing
in
the
sense
that
we'll
need
some
time
to
observe
if
there
are
any
new
occurrences
right
now,
I
think
there
are
around
four
or
something
like
that:
the
synchronizations.
A
A
But
given
that
I've
opened
an
issue
linked
it
in
this
layout
is
that
maybe
we
want
to
consider
if
there
are
any
other
attributes
that
we
want
to
keep
in
sync,
as
part
of
that,
so
that
we
run
this
migration
at
the
same
time.
So
basically
add
some
new
stuff
that
we
want
to
keep
in
sync
and
run
it
once,
rather
than
having
to
run
it
for
every
new
attributes
that
that
we
discovered
that
it
would
be
nice
to
have
it
on
the
on
the
project's
namespace.
A
So
yeah,
I'm
not
sure.
If
that
should
like.
We
should
query
some
other
teams
in
in
terms
of
what
features,
what
attributes
are
kind
of
similar
between
namespace
and
project
and
may
make
sense
to
to
keep
in
sync-
and
here
I'm
only
talking
about
basically
namespaces
table
and
project
stable.
I'm
not
considering
the
project,
settings
versus
group
settings
or
namespace
settings,
and
maybe
there
are
some
other
models
as
well.
That
will
be
nice
to
keep
in
sync.
A
So
that's
that's
out
of
this
question
now,
but
but
it
will
be
nice
between
the
two
tables
projects
and
namespaces
to
figure
out
what
are
the
attributes
that
will
be
nice
to
keep
in
c,
because,
like
the
path
is
one
thing
that
we
want
to
keep
in,
seeing
that
that
will
give
us
a
performance
edge
when
we
fetch
from
routes,
we
don't
have
to
go
back
to
the
project
to
fetch
the
project
we
we
can
go
right
to
the
project
namespace
and
fetch
that
instead
and
display
the
name
and
display
the
path
and
display
a
lot
of
stuff
right
from
the
namespaces
table
without
having
to
go
to
namespaces
and
then
to
project
right.
A
So
that's
that's
a
saved
query
there
and
a
lot
of
other
things
like
displaying
the
hierarchy
itself.
We
can
only
query
the
the
namespaces
table
because
we
have
all
the
names
and
and
descriptions
and
that
stuff
there
so
that's
again
some
performance
savings
and
so
on.
So
maybe
there
are
some
other
attributes
as
well.
B
I
think
we
should
also
like
I
understand
your
point.
On
the
other
hand,
I
think
it's
like
maybe
not
try
to
like
over
optimize
now
because
like
to
like
move.
Some
of
those
columns
to
the
from
foreign
space
also
require
some
some
work
on
that
code
side.
So
teams
may
not,
even
if
they
know
they
may
not
be
like
ready
to
do
it
now,
and
they
don't
want
to
block
it,
for
you
know
too
long
before
they
like
that,
they
are
ready
to
do
this
to
switch.