How to run transactions in Redis Database

preview_player
Показать описание
How to run transactions in Redis Database

Redis is an open-source, in-memory key-value data store. Redis allows you to plan a sequence of commands and run them one after another, a procedure known as a transaction. Each transaction is treated as an uninterrupted and isolated operation, which ensures data integrity.

The multi command tells Redis to begin a transaction block. Any subsequent commands will be queued up until you run an exec command, which will execute them.

🌸 Support channel & make donation :

🌸 Subscribe for more videos :

🌸 Follow me On Social Media

***********************************************************************

🌸 How To Check Bad Blocks Or Bad Sectors On a Hard Disk In Linux

🌸 Linux How To Partition a Hard Drive Using the Parted Command

🌸 Checking or Repairing a File System using fsck in Linux

🌸 How To Monitor the Health of Your Hard Drive in Linux using SMART

🌸 Linux iotop: Monitor your disk Input/Output

🌸 How To use the “du” (Disk Usage) Command in Linux

🌸 How To View Manipulate System Logs In Linux Using Journalctl Command

🌸 How To Sync And Backup Files In Linux Using Rsync Command

🌸 Linux cURL Command Tips and Tricks

🌸 Linux tail and multitail commands

🌸 Linux How To view Log Files

🌸 How To use the History Command On Linux

🌸 Tips and Tricks How To manipulate Text Files on Linux

🌸 How to Archive, Compress and Extract Files Using the tar Command on Linux

🌸 Linux - How to split larger files into smaller parts

🌸 Linux commands : Top

***********************************************************************
#Redis#Transaction#Database
Рекомендации по теме
Комментарии
Автор

4:50 if my understanding is correct, because the of the syntax error, the queued commands preceding the syntax error in the MULTI/EXEC transaction will not be executed.
I have been told however that if a command within the MULTI/EXEC throws an error during execution (eg running a LPOP command on a non-list key), then the queued statements will still be executed (and the state will therefore be half-way altered).
So I guess there's a difference between syntax errors, that throw errors during the queuing process, and command-errors that arise during the transaction execution.

galeop