aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMagnus Henoch <[email protected]>2017-09-14 16:58:53 +0100
committerMagnus Henoch <[email protected]>2017-09-14 17:07:18 +0100
commit9b5c49fd0c06459f2b2f8becc60a0fb70eb9d3ea (patch)
tree295aab36ceb0eb5ae3d9512bfd095017182198f8
parent94333e038485030f385012c99c0e7995ae03f499 (diff)
downloadotp-9b5c49fd0c06459f2b2f8becc60a0fb70eb9d3ea.tar.gz
otp-9b5c49fd0c06459f2b2f8becc60a0fb70eb9d3ea.tar.bz2
otp-9b5c49fd0c06459f2b2f8becc60a0fb70eb9d3ea.zip
Mnesia: note first, next, prev and last vs fragmented tables
In the Table Fragmentation documentation section, note that the functions first/1, next/2, prev/2 and last/1 return elements in an undefined order for fragmented tables. Also remove superfluous "the".
-rw-r--r--lib/mnesia/doc/src/Mnesia_chap5.xmlsrc6
1 files changed, 4 insertions, 2 deletions
diff --git a/lib/mnesia/doc/src/Mnesia_chap5.xmlsrc b/lib/mnesia/doc/src/Mnesia_chap5.xmlsrc
index 62759c624b..0265e0efa0 100644
--- a/lib/mnesia/doc/src/Mnesia_chap5.xmlsrc
+++ b/lib/mnesia/doc/src/Mnesia_chap5.xmlsrc
@@ -226,8 +226,10 @@
not known beforehand, all fragments are searched for
matching records.</p>
<p>Notice that in <c>ordered_set</c> tables, the records
- are ordered per fragment, and the the order is undefined in
- results returned by <c>select</c> and <c>match_object</c>.</p>
+ are ordered per fragment, and the order is undefined in
+ results returned by <c>select</c> and <c>match_object</c>,
+ as well as <c>first</c>, <c>next</c>, <c>prev</c> and
+ <c>last</c>.</p>
<p>The following code illustrates how a <c>Mnesia</c> table is
converted to be a fragmented table and how more fragments
are added later:</p>