this vid is confusing, the lossy decomposition example has an error
@tracynnnn15 күн бұрын
2:25 revisit
@pankaj205828 күн бұрын
worst case of binary search should be B not logB
@tracynnnn28 күн бұрын
For ARGMAX pt 2, why use the ALL keyword before the sub-query? Wouldn't it make more sense to use it at the start of the WHERE clause?
@tracynnnn28 күн бұрын
Difficult nested subqueries with correlation. Called relational "division"
@tracynnnn28 күн бұрын
**QUESTIONS** 1. What does the keyword IN do? 2. What is a nested sub-query? 3. What is a correlated sub-query? 4. What does the keyword EXISTS do? 5. What is the difference between ANY and ALL? **ANSWERS** 1. Allows to specify values in the WHERE clause 2. Runs first and once. The value returned is the value used in the outer/main query 3. A sub-query that executes for each tuple/row of the outer query 4. Returns TRUE if the sub-query returns one or more records 5. ANY will return TRUE should any records meet the conditions while ALL returns TRUE when _all_ the records meet the conditions
@llwa3500Ай бұрын
step 1:find boats a sailor has reversed step 2: these boats consist of all boats?(find the boats not in these boats,if find nothing ,it means these boats really consist of all boats) step 3: find sailors who have reversed all boats try something easier if the problem is hard
@papamujaffa5303Ай бұрын
at 0:12 he licks his lips
@daahirabukar4695Ай бұрын
😮
@sarynasser993Ай бұрын
thanks
@sarynasser993Ай бұрын
Thanks a lot
@doniyorvohidjonov704Ай бұрын
what is this? explained nothing
@nonameyet454Ай бұрын
I love jesus
@张馨月-g5v2 ай бұрын
useful!!❤❤ heart from china
@martdiamond96332 ай бұрын
What os check point, dirty page, clrLSN, LSN, redo, undo terms.
@RegattaData3 ай бұрын
I just found this, and while it may not be "fresh", it is absolutely EPIC and timeless. The beauty of concurrency control algorithms remains art as well as science - and hey, innovation is still happening there 🙂
@aglxru3 ай бұрын
I still don't understand why it's needed and what's the use of it in real life.
@holierthan4 ай бұрын
Gold!
@Adam-wt2ws5 ай бұрын
Is it a mistake that there is no 13, 17, and 30 anywhere in the leaf nodes of this tree?
@ukandumichael35556 ай бұрын
how can solve the left-deep in a query
@Tranquility_007 ай бұрын
Very clear explanation, easy to understand
@Go_with-Christ7 ай бұрын
god
@MrCk02127 ай бұрын
The "between" OP should also be allowed in the composite search key.
@moncefkoubaa59368 ай бұрын
u saved my life broo thanks a lott
@HsanEllouze-fj5dd8 ай бұрын
i think he saved our lifes
@amir_7alle98 ай бұрын
thank u
@jamm98489 ай бұрын
Thank you man, very helpful. 2 hours till exams and you made everything really clear
@aurumstinger44798 ай бұрын
how was the exam? Mine is tomorrow :)
@hohinng1969 ай бұрын
What are the steps of computing the average case of sorted file?
@florisred9 ай бұрын
This is gonna save me.
@tsunningwah34719 ай бұрын
zhian
@vikster29009 ай бұрын
🥲
@elfaidii9 ай бұрын
yo that's complicated but so cool
@yiran43210 ай бұрын
The range search of sorted file can be faster!!! Keep using binary search when you get the first number!
@menzo95092010 ай бұрын
god
@tsunningwah347110 ай бұрын
god
@abhishekvanenooru286910 ай бұрын
Berkeley professor i cant understand sab you make me sleep
@0i0l0o11 ай бұрын
This is really good. Thank you sir.
@NifeEsleman-q7o11 ай бұрын
Hi
@dongn4059 ай бұрын
hey
@WassupCarlton9 ай бұрын
@@dongn405 what up
@jeanie844811 ай бұрын
This was very helpful!!! Thank you 🙏
@SUYASHPUNDIR11 ай бұрын
awesome
@SUYASHPUNDIR11 ай бұрын
its great
@xpengineer11 ай бұрын
Thanks for the good videos. I am confused about writing an END log record for an Xact in the 'Committing' state without flushing the dirty pages before it. kzbin.info/www/bejne/rXanY2WdfqiHmpY. I searched the original paper, and the pseudo code shows that: "The only log records that may be written by this routine are end records for transactions that had totally rolled back before system failure, but for whom end records are missing". Is the paper talking about a different version of ARIES?
@davidespinosa1910 Жыл бұрын
Better: use a thread library that works.
@davidespinosa1910 Жыл бұрын
I actually thought databases were boring. :-)
@davidespinosa1910 Жыл бұрын
Not buying the hash/sort duality. But mergesort and quicksort are informally dual: mergesort = simple split, recursive sort, fancy join quicksort = fancy split, recursive sort, simple join.
@davidespinosa1910 Жыл бұрын
It's not 100% obvious how sorting and hashing work for duplicate detection. For sorting, see en.wikipedia.org/wiki/Weak_ordering For hashing, suppose we have a bucket with 100 elements in it. Are the elements unique ? Maybe, maybe not. So hashing by itself doesn't completely solve the problem.
@zxuhan79 ай бұрын
Hi, for hashing, i think these elements are not unique, but we can sort it very quickly, guaranteeing duplicate elements are adjacent together, the second phase of video 6 mentions this.
@davidespinosa19109 ай бұрын
@@zxuhan7 After hashing, we need to remove duplicates from each bucket. If we assume that the bucket size is bounded, then any algorithm is constant time. But we should state that assumption.
@zxuhan79 ай бұрын
@@davidespinosa1910 Yes, maybe video 6 from 5:00 can solve your problem. i think the buckets are not bounded in size, but since we only deal with one partition at a time, we can use in-memory algorithm to sort each bucket chain and make sure duplicate elements are together.
@davidespinosa1910 Жыл бұрын
Suppose we hash by gender, as in the earlier video. Then we have three values (M, F, O). This video makes it sound like all men are duplicates of each other, which makes no sense.
@davidespinosa1910 Жыл бұрын
When we compare numbers, we have n1 <= n2 and n2 <= n1 implies n1 = n2. But when we compare address records by name, this axiom fails: r1 = "Smith, John, New York" and r2 = "Smith, John, California". To solve this problem, the C++ sort function uses a strict weak ordering: en.wikipedia.org/wiki/Weak_ordering