Problems with Concurrent Execution of Transactions

  Рет қаралды 115,196

Edredo for Learners

Edredo for Learners

Күн бұрын

Пікірлер: 54
@invisiqueshadow5972
@invisiqueshadow5972 3 жыл бұрын
Maturity is when you realise that this is better than gate smashers.
@semthree5736
@semthree5736 3 жыл бұрын
Yeah bro..this is so good...
@shauntomy1277
@shauntomy1277 8 жыл бұрын
One of the best teachers i have seen, keep up the good work :)
@tejeshkonchada3971
@tejeshkonchada3971 4 жыл бұрын
Play at 1.25 times original speed. Thank me later
@stable_electron
@stable_electron 3 жыл бұрын
thank you! you time saver
@_sourav_
@_sourav_ Жыл бұрын
Playing at 2x still seems slow xD
@raghul867
@raghul867 3 жыл бұрын
I'm the only one who watching this with 2x speed before 10mins of exam.
@monsterrock8108
@monsterrock8108 2 ай бұрын
How was the exam bro 😆
@lordstinson8095
@lordstinson8095 7 жыл бұрын
What's the difference between "Unrepeatable read" and "Phantom Read" problem?
@ChandanYadav-hb6ux
@ChandanYadav-hb6ux 8 жыл бұрын
nice explanation.... please uploaded video on Concurrency Control..
@attacker21
@attacker21 Жыл бұрын
What a good explanation.
@moha_linus
@moha_linus 7 жыл бұрын
I don't understand English but i understand you hahaha It's very good explanation from u Thnx to much
@alibaba888
@alibaba888 4 жыл бұрын
Very simple and understandable, just what I was looking for thank you
@oliveryt7168
@oliveryt7168 2 жыл бұрын
Good explanation.
@anjalithakkar2259
@anjalithakkar2259 7 жыл бұрын
you hv a grt handwriting!
@CodeCraftWithVinayak
@CodeCraftWithVinayak 4 жыл бұрын
Excellent explaination thankx
@dfrontierit2114
@dfrontierit2114 3 жыл бұрын
Great video. Thank You
@CreazyFunFactsHQ
@CreazyFunFactsHQ Жыл бұрын
I like more and more what your explanation thanks more
@rakshitabandi9615
@rakshitabandi9615 2 жыл бұрын
thank you ,it was nice and simple explanation
@thakur_185.
@thakur_185. 7 жыл бұрын
excellent explanation
@vishnu32108
@vishnu32108 3 жыл бұрын
Nicely explained 👌 👏
@khoah9714
@khoah9714 8 жыл бұрын
Very good, thanks!
@jibeshbhattacharjee4306
@jibeshbhattacharjee4306 7 жыл бұрын
Neat. a very good idea for a youtube channel
@ChandanYadav-hb6ux
@ChandanYadav-hb6ux 8 жыл бұрын
nice explanation.. please uploaded video on topic in dbms like Dynamic Hashing ,Indexes ...
@pvksmaheeth8816
@pvksmaheeth8816 6 жыл бұрын
Nice explanation
@sanjeevsingh-nh4xj
@sanjeevsingh-nh4xj 6 жыл бұрын
does w(x) means writing update to database?????
@mohamedbalshy3105
@mohamedbalshy3105 Жыл бұрын
Designing data-intensive applications book is recommended
@venkateshchowdarapu5125
@venkateshchowdarapu5125 5 жыл бұрын
Sir in dirty read problem example how can T2 read the value of X as 110 instead of 100 which is not commited.
@sauravkumar7508
@sauravkumar7508 5 жыл бұрын
Because in t1 a write operation is performed after increasing the value of A.
@jeremiahazubuike3006
@jeremiahazubuike3006 6 жыл бұрын
thanks a bunch for the well organized and simplified explanations
@muthaiahpalaniappan8009
@muthaiahpalaniappan8009 8 жыл бұрын
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
@ShikhaMallick
@ShikhaMallick 8 жыл бұрын
Good explanation...
@rajatshetty10
@rajatshetty10 8 жыл бұрын
Thank you very much for the explanation sir....
@zhangxin1841
@zhangxin1841 4 жыл бұрын
what about dirty writes and write skew anomaly?
@AjwogTHUM
@AjwogTHUM 6 жыл бұрын
Thank you for this lesson
@amitasingh3581
@amitasingh3581 7 жыл бұрын
sir please prefer white background color it's comfortable to read with white bg
@SarbotamChatterje
@SarbotamChatterje 8 жыл бұрын
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
@wonkyochoe2093
@wonkyochoe2093 8 жыл бұрын
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
@bushrapirzada6776
@bushrapirzada6776 6 жыл бұрын
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
@aqeelar4121
@aqeelar4121 5 жыл бұрын
Helpful !
@thotakranthikumar2252
@thotakranthikumar2252 8 жыл бұрын
can u please provide a video on INCONSISTENT RETRIEVAL PROBLEM
@rajankumar5030
@rajankumar5030 5 жыл бұрын
really helpful
@Onella3DMusic
@Onella3DMusic 2 жыл бұрын
tysm
@vemulaakash8212
@vemulaakash8212 6 жыл бұрын
Thank you that is all I can say
@fabcotechnologies489
@fabcotechnologies489 4 жыл бұрын
CHeck out the Pi calculus and Rholang/RChain project, safe concurrent execution
@saiganeshmunduru5472
@saiganeshmunduru5472 8 жыл бұрын
well taught !!
@lakshayvinayak440
@lakshayvinayak440 6 жыл бұрын
Will u pls provide us notes of all the topics
@loveislulu264
@loveislulu264 5 жыл бұрын
what about multiuser anomaly?
@kumariabha1382
@kumariabha1382 7 жыл бұрын
sir pls make vedio on what are WR ,RW,WW problem plzzzzzz
@gozdec.1376
@gozdec.1376 5 жыл бұрын
thanks
@rohanchutke2298
@rohanchutke2298 6 жыл бұрын
thanks saved my arse !
@shambhavi_7957
@shambhavi_7957 8 жыл бұрын
i did not understand the last two ones incorrect summary and unrepeatable read can u please explain...
@rakib5969
@rakib5969 2 жыл бұрын
Are you Bangali ?
@Dnyaneshwar_Mulay
@Dnyaneshwar_Mulay Жыл бұрын
Wrong information shared
Transaction Failure, Recovery and Log
12:36
Edredo for Learners
Рет қаралды 111 М.
Number of Possible Schedules of given Transaction
13:03
Edredo for Learners
Рет қаралды 18 М.
Чистка воды совком от денег
00:32
FD Vasya
Рет қаралды 3,9 МЛН
Симбу закрыли дома?! 🔒 #симба #симбочка #арти
00:41
Симбочка Пимпочка
Рет қаралды 5 МЛН
WW Inconsistency: Lost Update Problem
7:04
Ritu Kapur Classes
Рет қаралды 9 М.
Recoverable and Nonrecoverable Schedules in Transaction
7:34
Edredo for Learners
Рет қаралды 96 М.
This is why understanding database concurrency control is important
9:05
Understanding Schedule and Conflict in Transaction Management
17:02
Edredo for Learners
Рет қаралды 43 М.
Building the Ultimate Workout Tracker with React Native & MongoDB
3:59:34
Dirty Read Problem| problems in concurrent execution of transactions | DBMS
7:41
KnowledgeGATE by Sanchit Sir
Рет қаралды 166 М.
Why view seriazability ? | Transaction Management
10:50
Edredo for Learners
Рет қаралды 30 М.
WR Inconsistency: Dirty Read Problem
6:46
Ritu Kapur Classes
Рет қаралды 6 М.