<transcript><audio_106>about so pay attention now all right so indexes point to object IDs to record IDs right imagine you have a slotted page organization it's going to say page number and the slot number now if I've got a primary key index and I could be</transcript><transcript><audio_107>updating the primary key and I'm making changes to that I now need to figure out how I'm going to keep track of that version change and version change stuff we can keep track of the techniques we talked about but now I have to go and update that primary key now it gets very</transcript><transcript><audio_108>tricky so often what happens when you're doing this versioning type of mechanism for primary key updates you'll basically treat it like a delete followed by an insert it makes the semantics clean and you won't have that version chain developed right because you delete</transcript><transcript><audio_109>everything's gone and do an insert okay the problem becomes more interesting with secondary keys because they're more complicated right in some sense the primary key controls the record right because you're accessing the record the record ID and the primary key in many ways are analogous so you can do these</transcript><transcript><audio_110>things like insert delete but for the second Ries you can't do that right there's a second riy and there's a very famous incident that happened at Uber a few years ago where they used to be on my SQL that had a good way of doing</transcript> about so pay attention now all right so indexes point to object IDs to record IDs right imagine you have a slotted page organization it's going to say page number and the slot number now if I've got a primary key index and I could be updating the primary key and I'm making changes to that I now need to figure out how I'm going to keep track of that version change and version change stuff we can keep track of the techniques we talked about but now I have to go and update that primary key now it gets very tricky so often what happens when you're doing this versioning type of mechanism for primary key updates you'll basically treat it like a delete followed by an insert it makes the semantics clean and you won't have that version chain developed right because you delete everything's gone and do an insert okay the problem becomes more interesting with secondary keys because they're more complicated right in some sense the primary key controls the record right because you're accessing the record the record ID and the primary key in many ways are analogous so you can do these things like insert delete but for the second Ries you can't do that right there's a second riy and there's a very famous incident that happened at Uber a few years ago where they used to be on my SQL that had a good way of doing
{"source": "grass-yt-cc-by.-mY8ALcJVTk|shard_1_1|create_multimodal_data.extract_yt_and_generate_transcripts.62|shard_1|create_multimodal_data.generate_captions.62|shard_1|create_multimodal_data.generate_captions.62", "params": {"id": "-mY8ALcJVTk", "channel_id": "UCHnBsf2rH-K7pn09rb3qvkA", "duration": 5000, "view_count": 4483, "age_limit": 0, "like_count": 50, "channel_follower_count": 71100, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@CMUDatabaseGroup", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_1/-mY8ALcJVTk.tar.gz"}}