Transcriptions
Note: this content has been automatically generated.
00:00:00
actually that a couple of them or fire when let your there's a a first form observables if
00:00:07
the date is change the database then the data will be changing the
00:00:12
you are immediately almost immediately centre yeah it will it will uh
00:00:16
on the other hand because you have an observable you're able to for example show as he says you know because of it
00:00:21
that saying that night and disappeared then you can just show pop up or something you know that would this happen
00:00:27
so does works with web so kids or something sorry i'm is this verse of web sockets
00:00:33
so get so kids yeah so i mean the underlying thing is kind of
00:00:37
a real time protocol rises i didn't but i don't have to do
00:00:40
with that as it were no no you don't have to deal with anything the only thing you deal with this observables and trying to do
00:00:55
but things would look will can go back to slide when you
00:00:58
talk about will not shuttle to use your instructions design
00:01:03
exactly there or yeah yeah yes all in this case how you
00:01:07
relate actually the to order id one is the same as
00:01:12
in both structures in the to the to do they have some idea
00:01:15
and then you can reference them to plunge yeah they're just saying
00:01:19
yes yeah thank you for the question first of all it yeah so the order id is probably what
00:01:23
not it it would be called for real it would be an i. d. that fire base would
00:01:26
generate for us so i'm just trying to make it uh usually visible for you guys but yes
00:01:31
uh order id one would you know correlate year as you see the colours so that's how
00:01:44
uh i have a question always possible to create of um user and
00:01:50
a lady that order and they are the um of of
00:01:59
rather the rollers and between the user id and or the
00:02:04
and number one the news or wireless uh um orders
00:02:11
oh go as well of course mm okay so you're saying basically that if we had to
00:02:19
a normal relational database we would have a problem right we try to delete an
00:02:24
user and that you should be referenced in a lot of collections the simple answer is
00:02:28
that you you that or the scary answer is that in adjacent database you wouldn't
00:02:32
have a it ever happening because it would just say this is a lot so
00:02:36
you're very responsible for making sure that your data i still you know atomic
00:02:40
so normally when it comes to databases you try to not use delete at
00:02:44
all right because we we tend to use delete flax and say
00:02:47
you know we set the bullion is this you know delete a true probably
00:02:51
so we i mean normally when you deal with databases you know don't ever delete because of these things
00:02:56
because foreign keys and i really think that should be a tactic that we use in these
00:03:17
it it people tend to solve that in a different way sometimes they only
00:03:21
store the user id sometimes distort the user id plus the name
00:03:25
or sometimes they store the entire user object but i'm trying to say that try to be a shallow that's possible so if you
00:03:32
it preferably is only the user id but if you really need to have the user id
00:03:35
plus the name but nothing more so try to make it as thin as possible
00:03:39
so you can refer to the actual heavy user objects in another collection
00:03:47
oh that is the uh and support for all flown functionality on the web
00:03:57
o. c. saying more like a progressive web apps that we would have it like a tactic for caching to
00:04:01
the local storage and you know once we get a connection it would try to do the actual reader
00:04:07
a very good question i don't know the answer i will have to find out and tell you
00:04:12
uh try to follow my tutor tiger will try to uh to address many answers as possible but i can't answer right now thank you
00:04:21
another question how sore backs ross or talk a um it's