►
From YouTube: XAFers Community Standup. EF Core Pitfalls and Solutions
Description
Click Here to Subscribe: http://xaf.life/35
Websites:
https://xafmarin.com/
https://xari.io
https://www.xafers.training/
http://xafersweekly.com/
Facebook Group
http://xaf.life/4g
Free XAF Support Hour
https://calendly.com/xari/free-xaf-support-hour
A
All
right,
all
right,
hey
welcome
everyone
to
another
example.
Community
stand
up.
I
think
that
today's
topic
is
a
really
interesting
one,
especially
with
the
direction
that
everything
is
taking,
we're
going
to
be
talking
about
identity
framework
and,
basically
things
that
we
are
using
XPO
and
now
we
are
getting
used
to
a
new
way
of
doing
things,
especially
in
new
projects
and.
A
Concurrency,
migrations,
property
change,
the
types
that
are
in
the
different
map
like
vulture
decimal
and
basically
talk
a
little
bit
of
the
Community
contributions
that
I
don't
know.
If
you
have
seen
there
is
a
column
model
that
already
someone
provide
there
is
their
Solutions
are
coming
along
the
way.
So,
as
always
before,
we
start
I
see
Hotel
Dave.
Here
we
also
have
a
really
good.
It
has
been
really
active
on
the
entity
finger
and
he
will
talk
to
us
about
this.
A
A
B
C
D
A
Yeah
so
before
we
start,
of
course,
this
is
the
article
that
Dev
Express
has
created
for
everyone
who
is
always
asking
hey.
Why
enter
the
framework
now
when
the
greatest
AB
solution?
One
thing
that
is
actually
got
me:
a
I
I,
don't
know
how
you
feel
about
this
man
I
understand
if
you
see
a
that
all
the
new
tutorials
for
anyone
getting
started
sent
to
the
frame
or
not.
A
A
So
taking
some
steps
in
that
regard,
if
we
go
to
my
tricky
I'm
going
and
you
see
all
the
Publix
repository
and
we're
going
through
all
of
those
ones-
and
we
are
migrating
it
here
and
holiday
because
we
want
to
be
safe
because
every
people
that
we
train
everyone-
we
always
make
them,
go
through
those
tutorials.
So
we
have
here
all
of
them.
I
hope
this
is
not
breaking
any
license
from
the
express
they
I'm,
pretty
sure
they
will.
A
Let
me
know,
but
we
took
a
step
forward
for
the
Spanish
community,
so
we
now
can
go
to
the
Spanish
and
we
will
have
all
of
these
tutorials
documentations
and
everything
also
in
Spanish.
So
if
they
are
struggling
with
the
language
barrier,
they
will
have
here
as
well.
All
of
those,
of
course,
I
still
have
to
create
some
type
of
page,
we'll
link
to
all
of
this
and
type
of
documentation.
Right
now,
it's
all
scattered
through
my
GitHub
but
I
think
at
least
we
have
a
place
that
we're
gonna
have
for
the
Spanish
Community.
A
All
these
tutorials
I'm
also
we're
gonna
talk
today
about
the
framework
back
and
forward.
I
would
say
it
beforehand,
I'm
not
in
love
at
all,
but
it
is
what
it
is
we
get
on,
and
there
is
a
lot
of
good
things.
I
think
that
there
is
also
a
lot
of
good
things,
but
it's
a
different
way
of
thinking
through,
but
coming
today,
article
right
here
there
is
a
the
like.
The
the
main
reasons
why
we
are
focusing
on
anything
different
now.
A
A
So
I
also
know
that
there
is
a
lot
of
and
I
think
one
of
this
one
here,
a
lot
of
discussion
about
the
multiple
active
resources,
because
that
means
that
for
a
any
other
engine
like
there
is
no
SQL
server
and
the
framework
is
having
some
difficulties
there
so
feel
free
to
read
all
of
this.
It's
a
good
trading
and
they
explain
everything
a
regarding
that,
but
a
let's
start
now
with
things
that
we
know
for
sure
that
are
not
out
of
the
box
on
many
different
out
of
the
box
and
the
different.
A
We
don't
have
software,
we
don't
have
the
at
least
not
how
we
are
used
on.
We
have
to
do
things
for
that
and
we
don't
have
concurrency
and
we
don't
have
the
migrations
on
the
database
automatically
that
you
add
a
property
and
right
away,
it
gets
updated
and
we
have
Solutions
like
for
all
of
those.
So
we'll
talk
today
about
here
and
and
go
from
there.
A
E
Yes,
good
ideas,
my
name
is
Sean
Paul.
Some
people
call
me
also
JP
or
jbt
whatever
we
are
developing,
also
in
craft
24
hours,
seven
days
a
week,
I
think
and
there
we
have
I
have
a
lot
of
experience
regarding
Entity
Framework,
not
in
combination
of
trough,
of
course,
because
it
was
lacking,
support
between
and
Entity
framework.
A
Got
it
okay,
thanks,
actually
I
have
to
mention
this
Empower.
We
reach
out
to
be
Empower
for
him
to
help
us
with
a
few
of
this
stuff,
so
he
has
been
all
Hands-On
and
he
has
been
a
lot
of
help
for
us.
So
thanks
again,
Japan
and
also
you
want
anything
as
to
what,
regarding
the
the
deletion,
the
property,
New
York
Gates,
all
of
get
cloned
out
the
trail
anything
you
want
to
go,
spinos
view
or
anything.
B
Well,
the
thing
is
that,
as
John
Paul
mentioned
is
not
quite
there
regarding
the
integration,
it's
not
like,
XPO
and
and
soft,
that
is,
it
looks
like
the
same
animal,
but
they
are
not.
Actually,
we
were
having
this
description
like
five
minutes
ago
before
we
start
the
meeting,
and
the
thing
is
that
Entity
framework
it,
it
is
a
little
bit
more
well,
it's
way
more
modern
than
XPO,
so
the
design
pattern
is
totally
different
and
they
try
to
provide
you
the
way
to
do
this
stuff,
but
not
do
them
for
you.
B
B
So
I
remember
that
fpo
used
to
get
a
lot
of
hate
because
people
don't
understand
it
in
some
cases,
but
now
that
people
is
moving
through
20D
framework
and
they
realize
XPO
did
all
this
functionality
for
us
now,
everyone
is
falling
in
love
with
a
with
the
with
the
whole
XPO
right.
So
the
purpose
of
this
meeting
is
to
try
to
make
a
bridge
and
show
everyone.
Okay.
This
is
how
we
are
used
to
do
it
in
XPO
in
Entity
framework.
B
A
A
A
If
you
go
to
migration
right
here,
there
is
the
the
steps
that
we
need
to
do.
Basically,
we
need
to
add
the
reference
to
our
this
novel
package.
The
Entity
framework
called
the
sign,
then
in
your
class,
the
the
same
time
factory
and
we're
gonna
check
that
one.
Basically,
this
is
a
commented
out.
This
other
part,
and
then
this
is
throwing
the
the
section.
So
basically
we
do
it
the
other
way.
We
comment
the
line
and
put
everything,
and
let's
put
it
here:
let's
follow
it,
the
redness
away
the
migration
commands.
A
And
if
you
see
here,
basically,
we
have
to
one
comment
out
this
and
comment
the
comment
out
of
the
the
section
and
after
that,
if
we
follow
the
the
tutorial,
we
make
sure
that
we
have.
They
don't
need
a
different
Global
tool,
and
then
we
do
our
migration
as
we
are
used
to
solve
this
first
thing,
do
is
open
further
and
valid
further
under
it
all
these
migrations.
A
Right
and
then
we
just
go
to
our
our
terminal
and
then
run
the
Oman
and
let's
do
like
Denise
Etc
so
right
here,
I
want
to
mention
that
if
you
like
I,
just
deleted
the
database,
if
you
run
the
application
by
default,
creates
database,
but
that
doesn't
create
a
migration
that
you
only
call
ensure
database
created.
So
if
you
do
this
a
migration
and
then
run
the
application,
software
create
the
database,
but
this
migration
hasn't
been
run.
So
when
you
are
trying
to
run
it,
it
will
tell
you
hey.
A
A
D
A
A
A
A
A
D
D
A
A
A
It's
not
there
yet
right
here,
there's
five
one
thing
that
actually
John
Paul
was
mentioning,
and
he
will
talk
about
this
a
bit
more
when
we
get
to
that
bar.
If
you
see
everything
that
is
Extreme
property
is
being
mapped
to
Manchester
Max
that
doesn't
make
sense.
I
think
that
it
should
be
the
different
I
know
that
we
have
and
I
will
we'll
see,
attributes
from
The
Entity
Franco,
but
there
are
better
ways
to
do
it
here.
D
A
I
think
that
this
is
one
of
the
things
that
I
have
seen
everyone
having
issue
with
I
have
I
haven't
met,
no
one
that
for
the
first
time
they
and
everyone
has
had
a
little
bit
of
issue
with
migration.
So
now
we
have
test
five
we're
good,
two,
all
right.
That
would
be
the
migration
part.
Okay,
I
think
that
the
a
good
next
feature
watching
will
be
if
you're
important
show,
is
a
concurrency
walk
around,
and
then
you
show
the
one
that
you
found
and
then
we
say
both.
That
would
be
a
great.
E
D
E
Perfect,
let
me
modify
the
yes
now
it
will
fit
yeah.
This
is
the
project
structure.
There
is
one
project
added
to
the
DB
migrator
and
that's
explained
in
the
readme
of
the
project,
but
within
the
module
we
have
a
lot
of
configuration.
Of
course,
I
started
with
one
sample.
This
is
a
book
sample
an
entity
that's
defined
over
here.
This
is
all
we
do
I,
don't
like
all
the
attributes
that
you
see
quite
often
with
the
New
York
soft
solution,
where
you
define
all
kinds
of
things
behind
the
scenes.
E
What
we
have
constructed
is
a
book
configuration
a
book
configuration
is
launched
when
entity
Frameworks
is
used,
and
in
this
case
we
use
this
method
to
place
a
prefix
on
the
table
even
use,
for
instance,
a
different
schema,
but
also
things
like
that.
Certain
Fields
has
a
different
language
in
characters.
So
in
this
case
it's
128.
E
It's
required.
If
you
look
at
xpl,
all
fields
that
are
constructed
are
nullable
and
are
not
required,
and
you
can
ask
do
I
rely
on
the
validation
module
and
put
a
lot
of
No
Strings
within
my
solution,
or
do
I
use
this
method.
This
is
the
same
as
adding
the
property
is
deleted.
That
mechanism
that
we
use
to
show
show,
delete
or
to
support
short
delete
by
default.
Everything
was
thrown
away,
is
or
what
is
deleted
in
xshop
will
be
a
hard
deleted
from
the
database,
but
sometimes
you
prefer
the
short
delete
method.
E
So
this
is
property
definition,
so
in
this
case
we
added
a
new
property.
That's
cool
is
deleted,
because
if
we
go
back
to
the
book
you
see
that
it's
not
defined
over
here
is
in
this
part,
we,
you
don't
see
the
property
back
in
the
configuration
we
added
a
property
as
as
an
additional
field.
It's
also
with
a
query,
a
mechanism
that
is
used
where
we
say
that
we
only
want
to
see
the
rows
that
are
not
deleted.
E
If
you
look
at
XBR,
we
use
a
GC
record
with
an
ugly
number
in
it,
and
in
this
case
we
use
Boolean
and
the
Boolean
should
be
false,
and
then
we
present
the
data
and
if
it's
not
false,
it
will
be
filtered
out
so
that
it's
not
visible
in
the
UI
Etc.
Then
we
have
another
property,
that's
the
price
where
we
showed
that
it's
money,
because
in
the
definitions
of
book
it's
decimal
over
here
and
where
is
it
a
decimal?
E
Resolution
and
data,
so
this
should
be
done,
all
the
property
budgets
can
be
removed
and
I
will
show
you
later
where
we
do
an
overall
here
we
do
this
trick.
This
is
this
part.
This
is
where
we
say:
every
column
should
be
everything
string,
column
should
be
treated
as
and
and
Fargo
100
show
I,
don't
like
the
the
max
value.
In
this
case,
all
columns
are
treated
as
100
and
in
this
case
a
decimal
is
mapped
to
money.
E
E
The
problem
is
that
we've
seen
that
we
changed
the
string
value
to
100,
but
certain,
like
the
report.
Where
is
it?
This
is
the
report
data.
Here
we
go
back
to
the
original
values.
As
you
can
see
within
XPO
show,
the
string
is
definitely
changed
to
a
length
of
100,
but
here
we
say
the
data
type
name
should
be
512,
and
this
is
a
definition,
as
you
would
find
back
also
in
your
HBO.
E
In
this
case,
we
override
all
the
the
xpl
or
the
the
values
that
are
not.
That
cannot
deal
with
100
characters.
So
in
this
case
we
go
back
to
Max
to
max
value.
So
this
configuration
it's
accessible
in
the
repository,
that's
online,
you
can
have
a
look
and
feel
the
book
is
over
here.
This
is
the
part
that
I
think
last
week
introduced
save
change
Interceptor.
This
gives
us
the
opportunity
to
when
the
book
is
shaved
during
an
insert
or
an
update.
E
We
can
deal
here
with
some
take
a
look
at
the
code.
In
this
case
we
iterate
to
all
the
entities
that
are
touched
by
the
modifications
or
the
inserts,
and
we
check
the
properties.
In
this
case,
we
check
if
it's
modified,
and
then
we
deal
with
properties
like
metadata.
The
original
file
in
the
current
file
I
think
that
the
latest
version
of
also
fixed
the
original
and
current
value,
but
in
this
case
we
have
access
at
the
change
tracker
and
the
entries
from
Brook.
E
E
E
E
This
is
the
the
standard
exception,
but
there
are
additional
exceptions
within
the
library
within
this
Library,
where
we
can
deal
with,
for
instance,
between
need
to
drill
down
to
the
interception
and
then
to
the
message.
If
you
take
this
one
and
then
there's
also
a
message
over
here,
then
you
get
a
stupid
message
like
unique
constraint,
violated
and
that's
it,
and
this
one
will
tell
the
property
is
violated
and
what
rule
is
throwing
this
exception.
So
this
is
a
more
detailed
one.
So
you
can
drill
down
in
specific
exceptions
over
here.
E
So
take
a
look
into
the
repository,
if
you
think
it,
if
you
want
to
play
with
it
or
if
you
have
questions
about
this,
so
I
think
that
yeah
there
is
a
lot
of
stuff
done
over
here.
There's
a
lot
of
configuration
work.
It
can
be
more
compact,
but
I
think
this
is
the
most
flexible
way
when
you
want
to
extend
it
yourself
yourself,.
E
B
E
Guess
because
I
have
some
interesting
things,
I
have
introduced
the
controller
over
here
a
couple
of
days
ago
regarding
I,
don't
know
if
you
have
seen
this
this
part
and
also
this
is
an
issue
of
course,
because
the
object
space
doesn't
affect
the
DB
context
and
also
not
the
the
change
tracker
so
yeah.
Sometimes
you
want
to
make
use
of
that
in
certain
parts.
E
I
have
to
check
out
if
the
validation
module
is
still
working
properly.
If
you
drill
down
to
the
context
over
here,
I,
don't
know
how
the
auto
Trail
is
dealing
with
data.
That's
changed
over
here,
and
so
that's
a
thing.
I
still
need
to
find
out,
because
the
at
Dev
Express
is
saying
that
you
should
not
go
this
path
to
drill
down
to
the
DB
context,
but
the
problem
is
the
API
of
entity.
Frameworks
is
much
function
rich
compared
to
what
the
current
object
space
is
offering
is
so
this
is.
B
E
D
E
This
case
I
go
to
the
I
change
to
the
context,
but
let's
say
that
I
change,
because
what
I
do
over
here,
I
I
checked
the
selected
books,
I
cast
them
to
an
array,
or
in
this
case
a
list
of
who
it's
good
and
then
I
change
the
books
again,
but
not
through
the
object
space
but
directly
through
the
context.
But
my
question
is:
if
I
do
this
modifications
on
the
selected
book?
Is
this
going
sorry.
B
I
and
I
can
I
can
tell
you
why
not
I
was
working
on
that
I
was
reading
this
Source
regarding
that,
and
this
is
what's
happening
when
you
do
stuff
when,
when
you're,
using
the
object
space-
and
you
say
like
create
object,
it
gets
created
by
an
activator
and
then
the
instance
get
attached
to
the
context.
So
right
now,
the
instances
that
are
attached
to
the
context
are
not
the
same
that
you
have
directly
with
the
with
the
DB
set.
B
So
I
think
that
what
we
should
do
is
between
all
of
us
take
a
look
to
the
to
The
Entity
framework
object
space
and
do
some
extensions
on
do
some
observations
on
what
we
would
like
to
have.
If
this
is
the
way
that
we're
going
like
what
we
would
like
to
have
available
for
the
object,
space
and
I.
Guess
it's
a
lot
of
extensions.
B
That's
the
way
to
go
to
extend
that,
but
definitely
we
need
to
take
a
look
on
how
staff
handles
the
the
the
creation
and
loading
of
objects
because
of
the
tracker,
because
that
is
so
is
so
it's
so
important
in
here,
because
some
of
some
of
the
examples
I
have
to
show
they
depend
on
the
tracker,
and
if
you
don't
attach
the
The
Entity
correctly,
it
becomes.
It
goes
crazy.
It
goes
crazy.
E
It's
Michael,
especially
if
you
look
over
here,
of
course,
where
we
say,
for
instance,
make
the
book
title
unique.
This
is
constraint
that
will
be
on
the
database
and
that
will
definitely
not
handled
correctly
through
the
validation
engine,
except
when
we
put
a
rule
into
the
entity
itself.
I
don't
have
the
actually.
This
is
the
wrong
one.
Where
is
my
business
object
over
here,
but
I
I?
Don't
have
the
rules
I
think.
B
B
Exactly
because
you
can,
what
usually
happens
in
normal
development
inside
is
that
you
maybe
you're
learning
and
you're
kind
to
trying
to
test
different
models,
so
you
define
an
object
like
the
title
should
be
unique.
The
titles
should
be
unique,
but
you
don't
have
the
rule.
Yet
you
enter
some
records
and
then
you
add
the
rule
that
rule
will
not
change.
The
database
will
just
change.
As
you
said,
it
will
work
in
the
UI
level.
B
B
B
Yeah-
and
it's
also
somehow
like
a
design
pattern
in
general
example,
because
you
can
do
that
by
adding
indexes
in
XPO,
you
will
have
a
really
ugly
exception,
but
then
you
handle
that
specific
exception
and
pass
the
information.
But
if
you
introduce
indexes,
you
can
have
the
same
effect
as
you
will
have
it
in
here.
Yeah.
B
It
depends
on
how
how
attached
you
want
to
to
be
to
your
DV
engine,
or
if
you
want
to
be
more
agnostic
and
in
here
I
guess
Javier
would
have
an
opinion
because
sometimes
it
for
me
I
like
to
do
the
stuff
in
the
code
way.
You
do
a
code
first
approach,
but
you
don't
change
database
engine
so
often
in
general,
or
almost
never
people
who
you
develop
for
SQL
survey.
They
developer
SQL
Server,
all
the
time
so
into
the
framework
is
it
can
be.
B
You
can
fine
tune
it
better.
For
me
into
the
framework,
it
seems
that
you
can
fine
tune
it
better
than
NT
dot
XPO.
Just
because
you
can
do
those
little
like
I.
Don't
know
like
use
the
specific
types
you
can
do
also
that
in
XPO,
but
it
looks
like
it's
more
on
the
surface
or
or
really
the
framework.
Yes,.
E
A
Don't
know
I
think
that
the
one
starting
we
should
hide
too
much
things
that
they
don't
have
to
do
at
the
beginning
and
then,
when
they
get
in
the
the
things
that
they
you
need
to
go
deep
and
customize,
then
they
can.
If
you
do
it
the
other
way
around.
You
are
having
a
level
of
complexity
that
is
I.
A
Don't
know,
I
think
that
this
animate
people,
when
they
are
trying
to
to
get
something
up
and
running
for
some
small
things,
so,
but
definitely
actually
I,
think
that
the
dev
Express
answer
will
be
hey
you
Google
and
in
the
different
workcore
solution,
so
kudos
to
you
and
go
for
it.
Keep
going
all
right.
I
want
to
to
mention
something
that
I
should
have
mentioned
at
the
beginning
of
the
foreign
I
will
do
it
again
at
the
end:
hey
I,
probably
edit
the
video
and
put
this
disclaimer
at
the
beginning,
okay
of
the
middle.
A
Let
me
check
my
screen
and
watch
I
will
give
you
the
screen
right
away.
So
this
is
a
ticket
that
Danny.
He
said
we
do
not
encourage
or
a
migrations
if
you
have
been
using
XPO
for
a
long
time
and
you
have
a
big
system.
This
is
not.
You
don't
have
to
migrate
to
Entity
framework.
Just
because
now
you
see
things
are
XPO
works
and
they
say
we
have
not
done
that.
It
will
not
be
an
easy
replacement.
I'm,
just
letting
you
guys
know.
A
I
have
a
customer
that
we're
going
through
that
right
now
and
a
and
confident
that
he
did
it
just
for
the
article
of
direct
express
why
we
are
choosing
the
Entity
framework
instead
of
HBO,
the
one
that
we
showed
the
beginning,
but
that
should
be
for
new
projects.
If
you
have
a
huge
project
that
you
already
maintained,
that
he
has
to
work
with,
no
issues
that
you
are
there
is
no
need,
please.
There
is
no
need
for
you
to
go
through
all
the
trouble,
all
the
hassle
of
both
20
different.
A
D
A
B
Yeah,
let's
see
okay,
so
we're
going
to
do
a
huge
bridge
between
being
in
Chile
and
my
machine
at
home.
So,
okay,
this
is
also
in
a
public
repo.
We
did
this
test
in
two
different
ways.
We
did
them
along
with
Entity
framework,
only
not
stuff,
and
then
we
move
all
of
them
to
stuff.
So,
as
John
Paul
explained,
there
are
several
ways
to
do
things.
You
know
the
framework
and
one
of
the
ways
that
we
kind
of
like
is.
Let
me
show
the
solve
the
lead
first.
B
See
two
properties,
not
extra
property,
to
handle
the
the
is
deleted
and
what
we
do
is
we
create
a
configurator
class
and
this
configurator
class.
We,
as
also
young
poll,
show
we
extended
with
the
in
the
binder.
We
tell
them,
we
add
the
property
is
deleted
and
then
we
add
a
filter
to
say:
okay,
when
exclude
when
you
get
when
you
use
the
DB
set.
Give
me
all
the
records
where
is
deleted
is
equal
false
when
you
do
two
lists
on
the
DB
set.
B
So,
on
the
on
model,
creating
you
can
get
the
mobile
Builder
and
then
apply
configurations,
and
what
is
neat
about
this
is
that
you
can
do
this
in
xaf
with
the
types
info
you
can
add
like
attributes
and
modify
the
types,
but
in
here
we
are
adding
soft
delete
to
the
object
that
I
just
showed
you
before
is
so
delete
here,
or
you
can
also
add
to
a
different
object.
That
is
not
even
this.
B
A
Striving
for
is
that
all
of
these
configurator,
all
of
those
things
to
try
to
to
find
a
way
to
do
an
engineering
way
like
for
every
object
or
things
like
that,
for
example,
or
the
migrator.
Do
it
in
the
same
project
or
like
jump
out,
show
a
place
that
all
strings
goes
to
the
just.
The
bar
chart
100.
So
this
type
of
settings
that
go
globally
instead
of
having
to
do
one
by
one.
B
B
D
D
B
B
B
The
tracker
has
like
this
proxy
object
with
all
the
values
and
everything
that
changing
the
object
and
we're
asking
if
any
of
the
members
name
is,
is
deleted,
then
go
into
Dave
right,
so
the
entity
has
a
state
if
it's
added,
if
it's
deleted
and
so
on
and
so
forth.
So
if
it's
added
we
can
put,
the
is
delete,
equals
false,
and
if
the
entity
is
deleted
in
the
lead
to
the
state,
then
we
mark
it
a
stroke.
B
B
B
Registration,
it
will
not
be
here,
but
if
I
go
here
and
I
eat
this
record
and
I
set
it
to
false,
then
when
I
refresh
I
will
see
it
back
again
in
the
UI
see,
and
that
might
happen,
because
when
we
did
the
configurator
for
the
for
that
entity
with
told
something
like
Okay,
add
this
column
and
also
add
this
filter,
which
is
this
one
here.
So
we
are
excluding
everything
that
this
Market
has
deleted.
B
You
can
even
actually
Paul
mentioned
here,
we're
setting
the
state
back
to
modify
here
instead
of
just
adding
a
simple
true.
You
can
add
at
times
something
that
makes
sense
for
your
business
logic,
so
you
are
able
to
restore
it
later
if
you
want,
but
in
the
most
simple
case,
just
like
a
Boolean
Mark
is
is
more
than
enough.
C
D
D
B
E
To
yeah,
the
aggregated
collections
should
be
provided
also
with
this
property
or
with
this
mechanism.
So
also,
if
you
don't
do
that,
the
collections
will
be
deleted
forever.
But
if
you
make
the
aggregated
collections
also
using
the
same
soft
Elite
support,
then
they
will
be
a
short
deleted
through
yes,
very
good.
Thank
you.
A
B
B
So
if
you,
if
you
go
to
this
object,
we
are
still
integrating
from
the
base
objects
from
xaf,
and
if
you
use
this
attribute
like
the
timestamp
attribute,
this
will
be
timestamp
that
will
be
automatically
increased
by
Entity
framework
without
any
additional
code.
So
this
timestamp
will
serve
as
a
road
version,
which
means
that
if
two
people
have
the
same
record,
it
will
check
the
row
version
or
the
timestamp
to
make
sure
that
this
update
in
the
right
exact
object.
B
So
in
this
case
it's
as
simple
as
doing
this,
of
course,
you
should
Mark
this
as
non-prossable
in
such
because,
if
not,
you
will
see
it
in
the
UI
and
there
is
a
second
grade
that
I
will
explain
just
a
little
bit
later.
But
let
me
go
to
the
controller
to
explain
this,
because
we
have
a
controller
for
that.
B
We
create
an
object
in
code
with
one
object
space.
Then
we
commit
that
object
space.
Then
we
read
the
same
object
in
two
different
orders
object
spaces,
and
then
we
compete
in
one
and
try
to
commit
it
in
the
second
one
that
will
create
a
concurrency
problem
because
both
of
them
create
the
same
file.
But
once
it's
time
to
commit
the
record
has
changed
because
one
of
one
of
them
already
committed
changes.
So
the
second
case
will
this
will
fail.
Actually,
so
let's
run
that
so
this
concurrency.
B
B
B
So
here
they
say
like
okay,
the
database
operation
basically
failed.
So
there
was
no
rows
affected
is
because
of
the
concurrency,
so
it's
kind
of
the
automatic
easy
way
to
do
it.
There
is
also
a
different
way
at
their
way,
because
John
Paul
show
one.
This
is
the
second
way
and
there
is
a
third
way
to
do
it,
which
is
you
can
Mark
any
of
your
properties
as
concurrency
check.
B
The
main
difference
between
the
timestamp
and
the
concurrency
check,
and
here
you
can
see
what
I
wrote
about
it
is
that
for
the,
if
you
mark
something
with
the
concurrency
check
attribute,
it
means
that
you
are
in
charge
of
increasing
the
value
or
changing
the
value
in
any
way
to
make
the
row
these
things
from
each
other.
So
this
one
I
will
not
use
it
because
I
don't
increase
the
value,
but
if
you
haven't
mechanism
yourself
to
increase
the
value
or
to
make
the
the
value
be
different,
all
the
time
you
can
use
this.
B
This
can
I
think
can
be
useful
in
a
legacy
model
where
you
have
something
like
that
already
implemented.
That
database
level
or
whatever
so
you
can
mark
it
as
concurrency
check
column
but
you're
in
charge
to
increase
the
value
or
change
change
the
value
actually
not
increase.
At
least
it's
not
necessarily
a
numeric
number.
So
that
is
the
other
way
and
Javier
do
you
want
to
show
the.
A
Let's
do
something
like
I
can
guide
you.
Why
I
think
that
we
should
show
I
think
that
we
should
show
now
the
loving,
that's
just
a
piece
of
code.
We
don't
have
to
show
anything
else
and
then
okay,
okay,
the
way
we
see
in
the
low
in
the
queries
that
the
attach
is
generating-
and
why
do
we
think,
okay.
B
B
You
can
just
write
it
to
the
the
console
or
get
that
value
from
there
and
save
it
in
whatever
place
you
want
to
save
it
in
another
database
in
a
file,
an
XML
or
whatever
that's
one
way,
and
the
second
way
is
that
you
can
create
a
lower
Factory
and
in
the
lower
Factory.
You
have
the
same
pattern
of
like
extensions
and
on.
B
And
configuration
so
in
here
you
can
tell
okay
I
want
to
label
Jaws
in
this,
like
just
information,
just
warnings
use
exceptions
or
whatever,
and
then
you
add
the
output.
This
can
be
debug
or
consult
any
of
those
and
something
that
is
really
important.
This.
If
you
do
it
just
like
this,
you
will
log
only
the
the
query,
but
not
the
parameters
value,
so
you
will
log
the
insert,
but
you
will
not
know
what
you.
What
are
you
inserting?
B
If
you
want
to
see
what
you're
inserting-
and
this
came
from
John
Paul?
Also
you
have
to
enable
sensitive
data
loading
that
will
include
the
query
and
the
parameters
value.
So
you
will
see
like
you
will
see
the
insert
and
you
will
see
each
of
the
parameters
that
you
are
inserting
which
value
it
has
right.
Now
we're
actually
running
with
this
so
and
I.
Guess
it's
the
perfect
time
to
show
the
the
attach
functionality.
So
the
touch
is
the
idea.
B
B
What
you
do
is
knowing
something
about
the
object
you
can
attach
it
and
start
tracking
the
changes.
So,
for
example,
in
here
we
have
almost
the
same
case
as
the
concurrency
actually
the
same
object.
We
create
an
instance
and
then
we'll
be
committed
to
the
database.
Then
from
that
instance,
we
get
the
ID
on
the
timestamp.
B
We
need
a
timestamp
for
one
reason,
because
we
need
to
tell
them
it's
the
same
raw
version
that
we
were
using
before,
because
we
are
using
the
concurrency
check
in
this
object.
If
we
were
not
using
that,
basically,
you
don't
need
to
add
this
line.
This
is
just
extra
because
of
the
concurrency
check
and
you
will
see
it.
It
will
make
sense
when
we
see
the
query
so
then
what
happened
is
like
I
can
create
a
proxy.
B
B
So
it
will
assume
that
this
object
was
loaded
from
the
database
as
instead
of
loading
it.
It
will
assume,
because
it
has
the
proper
information
to
track
it,
which
is
the
timestamp
and
the
ID,
and
then
we
get
the
DB
context
and
we
attach
it
and
then
basically,
with
the
object
space,
we
delete
this
object
and
we
commit
the
changes.
So
what?
What
does?
What?
What
will
happen
in
here
is
that
we
will
commit
the
object.
B
We
will
create
an
object
in
memory
that
we
know
the
timestamp
and
ready.
We
delete
it.
So
we
don't
know
that
again
from
the
database
and
you
will
see
the
query
that
that
it
gets
generated.
So
let's
run
this
because
I
found
this
beautiful
in
the
case
of
mass
updates
and
and
mostly
there
was
one
extension
for
XPO
located
by
Robert
Anderson
zero
Sharp.
That
did
something
like
this
for
mass
delete
and
master
updates.
B
So
let's
clear
this-
and
you
will
see
that
there
are
no
other
queries
from
here
on
when
we
continue,
we
already
attach
an
object.
So
this
object
that
is
attached.
It
has
the
well
here
you
can
see
it.
You
can
see
the
idea
here
in
the
in
this
tooltip
and
if
I
delete
it,
it
will
just
create
the
delete
query
and
when
I
commit
the
optic,
it
will
just
happen
easily.
The
market
has
deleted.
Then,
when
I
commit.
B
You
see
here
delete
from
and
there
were
ID
and
timestamp
both
need
too
much.
If
I
only
have
the
the
If
I
Only
Had
the
ID,
it
will
tell
that
there
is
a
concurrency
error,
because
it's
not
the
same
you're
deleting
a
record
that
someone
else
has
changed,
because
you
will
have
a
different
timestamp.
So
this
is
really
nice
and
kind
of
really
simple
here.
The
implementation
so
I
will
put
the
the
link
for
this
repo,
also
in
the
chat,
so
you
can
grab.
A
A
B
They
both
have
this
set
property
value
which
matches
the
same
signature
and
name
of
the
set
property
value
of
XPO.
In
here
I
I
wrote
that
method.
It
doesn't
come
from
the
base
because
this
doesn't
have
any
special
base
and
what
we
do
is
basically
we
check
if
the
property
value
is
the
same
as
the
one
that
we
had
before
and
if
it's
the
same,
we
just
return.
We
don't
delete
the
notification
and,
if
is
different,
we
call
the
unchanged
method
that
I
actually
wrote
this
Knight
method.
You
can
make
it
full.
You
can
build.
B
Also
you
can
see
it
in
the
OR
protected
virtual,
so
you
can
see
it
in
the
base
classes
so
in
the
child
classes,
and
then
we
invoke
the
the
property
change
for
everyone
that
is
listening
to
this.
We
pass
these
arguments
and
also
you
can
understand
the
arguments
you
can
inherit
from
that
class.
They
all
value
to
that
argument.
B
B
B
A
Thing
that
I
want
to
add
I
think
that
this
is
important.
I
might
be
crazy,
but
I
think
that
the
first
version
of
the
vessel
is
romantic
different
world.
It
had
I
notify
property
change.
Implement,
then
that's
not
the
case
anymore
I.
Don't
know
why
I
think
that
I
probably
should
go
back
and
verify
right
now
only
have
eyeshaft
enter
the
object
and
either
especially
and
throw
the
change
proxies.
I,
don't
recall
exactly
they
inject
the
inertified
property
chain.
A
So
the
main
point
here
with
what
the
hotel
show
is
that,
okay,
you
know
right
here,
you
only
have
to
put
a
get
on
set
and
the
notified
property
chain
gets
injected.
You
don't
have
to
take
care
of
that
you're
good,
to
go
at
the
same
moment
that
you
other
explicity,
as
Jose,
had
to
put
the
same
property
value.
If
you
miss
in
any
of
your
property
that
set
property
value
over
their
own
change,
so
that
explicit
implementation,
it
will
not
notify.
A
So
you
have
to
make
sure
that
if
you
have
your
object
and
you
both
I
notified
property
chain
here,
for
any
reason
you
have
to
do
it
to
every
property
or
it
will
not
work.
It
will
only
so
right
here
if
it
doesn't
have
any
get
injected.
If
we
have
an
explicitly
you
have
to
do
it
just
keep
that
in
mind,
because
that
virus
later
last
week,
so
we
say
why
is
this
not
working,
and
it
was
just
an
oversight
offers
on
our
side.
A
So
that's,
basically
it
I
don't
want
to
make
the
the
middle
too
long.
I
think
that
we
have
covered
a
lot
of
things
on
Entity
framework.
I
will
definitely
would
love
to
hear
some
feedback,
or
especially
people
that
are
using
Entity
framework
with
a
different
database
than
SQL
server
or
any
other
things
that
you
guys
are
playing
with
or
doing
and
any
solution
that
you
guys
find.
Please
let
us
know
both
repos.
Let
me
just
move
this
over
here.
A
Both
ripples
are
public
right
now
this
is
the
one
from
John
Paul.
This
is
really
good
one,
and
this
is
the
one
that
coach
has
on
this
repo.
Also,
this
is
a
ticket
from
Japan
that
he
pulled
like
I
think
a
couple
months
ago
to
I
think
that
is
a
really
good
one.
It
goes
to
a
lot
of
things.
He
doesn't
go
only
to
the
elite
issue
that
the
okay
space
is
the
leading,
doesn't
report
correctly,
but
it
also
talks
about
things
that
he
has
tried,
and
things
are
amazing
and
so
on.
A
It's
just
a
good
overview.
We
have
this
course
most
of
them
here,
but
basically
I
think
that
is
a
great
read
right
here
is
the
object,
change
all
and
new
value,
and
the
issue
around
that
right
here
is
the
same
thing
about
the
field
sizes
ignore
and
basically,
which
will
use
the
attributes
for
the
framework,
and
this
is
again
a
big
like
to
do
it
say
it
again.
We
do
not
encourage
our
migration
from
XP
into
the
framework
if
you
have
a
Lego
a
product
that
is
a
huge
and
you
have
been
using
it.
A
There
are
a
lot
of
things
that
you
will
have
to
do.
They
will
not
be
an
easy
replacement.
We
cannot
support
you
on
this
migration
and
the
errors
that
you
experience
and
the
express
have
not
done
it
yourself,
I'm,
not
planning
to
publish
migration
guidelines,
so
we
are
going
through
that
right
now.
So,
if
we
can
help,
we
probably
will
be
documenting
some
migrations,
but
I
will
definitely
say
if
your
system
is
running
and
working.
You
should
not
entail
this,
but
that
will
be
my
my
two
cents.
A
I
still
love
XPO
I
still,
this
is
what
I
will
keep
using
in
all
my
products,
the
only
time
that
I
will
use
and
to
defend
what
is
when
a
clients
requires.
If
that's
not
the
case,
if
I
have
complete
control
of
the
RN,
it
will
be
XPO.
That's
my
two
cents,
everyone
who
wants
to
work
anything
if
not
take
your
time
and
anything
and
anything
that
we
did
not
cover.
A
Let
us
know
so
we
do
a
follow-up,
because
if
you
see
I
think
that
we
are
still
improving,
the
Empire
has
a
solution
then
with
another
one,
then
we
are
reviewing
like
different
way
of
doing
something.
Then
we
are
finding
something
like
the
I
notify
property
change.
The
half
was
frequency,
there's
another
part
of
the
representation,
so
this
will
be
evolving.
I
believe
that
we
will
get
to
a
really
nice
set
of
features,
but
if
you
have
one,
if
you
solve
one
of
those
issues,
please
let
us
know.
D
E
A
A
The
community
here
is
important.
Now
we
support
each
other
and
anything
that
we
like
solve.
Please
share
live
again
that
will
help
us
everyone
to
build
some
more
powerful
base
for
anything
different
because
even
and
I
will
we
have
discussed
this
even
if
the
express
say
that
Entity
framework
is
so
much
is
matched
with
XPO
internal
of
sub
support.
I,
don't
think
that's
the
case.
Hbo
has
been
with
South
since
day,
one
so
definitely
I
believe
you
can
do
everything
that
you
do
with
XPO.
A
You
can
do
it
in
South,
but
it's
not
the
same
level
of
support.
It's
not
the
same.
At
least
it's
at
least
I
have
to
get
used
to.
Let's
say
that
there
is
a
lot
of
things.
That
is
not
the
right
the
same
way
as
we
are
used
to
it.
There
is
a
lot
of
more
things
to
having
account
more
code
to
board
more
things
that
were
out
of
the
box.
So
definitely
this
is
where
the
community
plays
a
big
part.
Anything
we
can
help
each
other.
That
would
be
the
idea
here.