IS IT A DIRTY READ CASE DURING LOST UPDATE PROBLEM? I THINK NO, COS THE VALUE OF X IS NOT YET WRITTEN IN COLUMN 1 AND THE VALUE IS STILL 100 FOR X IN COLUMN 2.. PLZ EXPLAIN. 5:10
I'm not sure what your are trying to say but if I understand correctly, that is not a "dirty read case". The problem of above schedule in Lost update problem is that T1, T2 are not serializable. In other words, that schedule is wrong case since T2 will read not-updated "x" value from Hard disk. In this case, all transaction will be terminated or committed without abort but x will be a wrong value. In contrast, in dirty read case, x must have a original value because T1 has been aborted. But, T2 still have a changed "x" value. So, this case is not a updating problem. I wrote this knowledge as far as I know. If you find any incorrect information about above comment, please make correction
Yes you are right, the word itself says DIRTY READ, means a failed value is read by some other transaction, and a value is read by other transaction only if it is written(write) first
Sorry for my ignorance...but what is the use of writing to the Database??? It can commit directly while it writes to the table, right??, why is this intermediate step of writing to Database? If it's really required can you give me an example, at which point it may failed to commit when the write is successful. Thanks
Maturity is when you realise that this is better than gate smashers.
Yeah bro..this is so good...
One of the best teachers i have seen, keep up the good work :)
I'm the only one who watching this with 2x speed before 10mins of exam.
How was the exam bro 😆
Play at 1.25 times original speed. Thank me later
thank you! you time saver
Playing at 2x still seems slow xD
What's the difference between "Unrepeatable read" and "Phantom Read" problem?
Thank you for this lesson
nice explanation....
please uploaded video on Concurrency Control..
What a good explanation.
Good explanation.
Very simple and understandable, just what I was looking for thank you
I don't understand English but i understand you hahaha
It's very good explanation from u
Thnx to much
IS IT A DIRTY READ CASE DURING LOST UPDATE PROBLEM? I THINK NO, COS THE VALUE OF X IS NOT YET WRITTEN IN COLUMN 1 AND THE VALUE IS STILL 100 FOR X IN COLUMN 2.. PLZ EXPLAIN. 5:10
I'm not sure what your are trying to say but if I understand correctly, that is not a "dirty read case". The problem of above schedule in Lost update problem is that T1, T2 are not serializable. In other words, that schedule is wrong case since T2 will read not-updated "x" value from Hard disk. In this case, all transaction will be terminated or committed without abort but x will be a wrong value.
In contrast, in dirty read case, x must have a original value because T1 has been aborted. But, T2 still have a changed "x" value. So, this case is not a updating problem.
I wrote this knowledge as far as I know. If you find any incorrect information about above comment, please make correction
Yes you are right, the word itself says DIRTY READ, means a failed value is read by some other transaction, and a value is read by other transaction only if it is written(write) first
you hv a grt handwriting!
Excellent explaination thankx
excellent explanation
Nicely explained 👌 👏
Very good, thanks!
Great video. Thank You
does w(x) means writing update to database?????
Sir in dirty read problem example how can T2 read the value of X as 110 instead of 100 which is not commited.
Because in t1 a write operation is performed after increasing the value of A.
thank you ,it was nice and simple explanation
what about dirty writes and write skew anomaly?
I like more and more what your explanation thanks more
nice explanation..
please uploaded video on topic in dbms like Dynamic Hashing ,Indexes ...
Neat. a very good idea for a youtube channel
Nice explanation
Thank you very much for the explanation sir....
Helpful !
Sorry for my ignorance...but what is the use of writing to the Database???
It can commit directly while it writes to the table, right??, why is this intermediate step of writing to Database? If it's really required can you give me an example, at which point it may failed to commit when the write is successful. Thanks
Good explanation...
Thank you that is all I can say
thanks a bunch for the well organized and simplified explanations
Will u pls provide us notes of all the topics
really helpful
well taught !!
tysm
Designing data-intensive applications book is recommended
what about multiuser anomaly?
can u please provide a video on INCONSISTENT RETRIEVAL PROBLEM
thanks
CHeck out the Pi calculus and Rholang/RChain project, safe concurrent execution
sir please prefer white background color
it's comfortable to read with white bg
thanks saved my arse !
sir pls make vedio on what are WR ,RW,WW problem plzzzzzz
Are you Bangali ?
i did not understand the last two ones incorrect summary and unrepeatable read
can u please explain...
Wrong information shared