Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
S
StackExchange.Redis
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
tsai
StackExchange.Redis
Commits
6c555283
Commit
6c555283
authored
Mar 21, 2014
by
Marc Gravell
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #2 from matteobaglini/patch-2
Fix command
parents
a92d7ff3
44d2409c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
Transactions.md
Docs/Transactions.md
+2
-2
No files found.
Docs/Transactions.md
View file @
6c555283
...
@@ -8,7 +8,7 @@ A transaction in redis consists of a block of commands placed between `MULTI` an
...
@@ -8,7 +8,7 @@ A transaction in redis consists of a block of commands placed between `MULTI` an
has been encountered, the commands on that connection
*are not executed*
- they are queued (and the caller gets the reply
`QUEUED`
has been encountered, the commands on that connection
*are not executed*
- they are queued (and the caller gets the reply
`QUEUED`
to each). When an
`EXEC`
is encountered, they are
to each). When an
`EXEC`
is encountered, they are
all applied in a single unit (i.e. without other connections getting time betweeen operations). If a
`DISCARD`
is seen instead of
all applied in a single unit (i.e. without other connections getting time betweeen operations). If a
`DISCARD`
is seen instead of
a
`
MULTI
`
, everything is thrown away. Because the commands inside the transaction are queued, you can't make decisions
*inside*
a
`
EXEC
`
, everything is thrown away. Because the commands inside the transaction are queued, you can't make decisions
*inside*
the transaction. For example, in a SQL database you might do the following (pseudo-code - illustrative only):
the transaction. For example, in a SQL database you might do the following (pseudo-code - illustrative only):
// assign a new unique id only if they don't already
// assign a new unique id only if they don't already
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment