Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
T
tarantool
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
core
tarantool
Commits
9c322691
Commit
9c322691
authored
11 years ago
by
ocelot-inc
Browse files
Options
Downloads
Patches
Plain Diff
errcode.xml minor change
parent
397b6d6d
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/user/errcode.xml
+1
-8
1 addition, 8 deletions
doc/user/errcode.xml
with
1 addition
and
8 deletions
doc/user/errcode.xml
+
1
−
8
View file @
9c322691
...
...
@@ -7,7 +7,7 @@
<para>
In the current version of the binary protocol, error message,
which is normally more descriptive than error code,
is not present in server response. The actual message may contain
a file name, a detailed reason or operating system error code.
a file name, a detailed reason or
an
operating system error code.
All such messages, however, are logged in the error log. When
using
<emphasis
role=
"strong"
>
Memcached
</emphasis>
protocol, the error message is sent to the
client along with the code. Below follow only general descriptions
...
...
@@ -45,13 +45,6 @@ file <filename xlink:href="https://github.com/tarantool/tarantool/blob/master/in
</para></listitem>
</varlistentry>
<varlistentry>
<term
xml:id=
"ER_INDEX_VIOLATION"
xreflabel=
"ER_INDEX_VIOLATION"
>
ER_INDEX_VIOLATION
</term>
<listitem><para>
A unique index constraint violation: a tuple
with the same key is already present in the index.
</para></listitem>
</varlistentry>
<varlistentry>
<term
xml:id=
"ER_KEY_PART_COUNT"
xreflabel=
"ER_KEY_PART_COUNT"
>
ER_KEY_PART_COUNT
</term>
<listitem><para>
Key part count is greater than index part count
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment