Documentation Source Text

Check-in [5702963af2]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Correct typos noted in Forum post f381c42ab1.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 5702963af267b0abd6b942c6bcf6e73127c16414714482b7dab627370f75c86d
User & Date: larrybr 2023-01-25 10:47:31
Original Comment: Correct typos noted in [forum:forumpost/f381c42ab1|Forum post f381c42ab1].
Context
2023-01-27
02:15
Correct generate_series() mistakes noted in [forum:forumpost/c2101840f1|forum post c2101840f1]. (check-in: 96a13a1c67 user: larrybr tags: trunk)
2023-01-25
11:14
Correct typos noted in Forum post f381c42ab1. (check-in: 8e3ddbd5b8 user: drh tags: branch-3.40)
10:47
Correct typos noted in Forum post f381c42ab1. (check-in: 5702963af2 user: larrybr tags: trunk)
2023-01-21
23:07
Typo fixes in JSON documentation. (check-in: 7f680aab5f user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/fileformat2.in.
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
<p>^If the PRIMARY KEY of a WITHOUT ROWID tables uses the same columns
with the same collating sequence more than once, then the second and
subsequent occurrences of that column in the PRIMARY KEY definition are
ignored.  ^(For example, the following CREATE TABLE statements all specify
the same table, which will have the exact same representation on disk:

<blockquote><pre>
CREATE TABLE t1(a,b,c,d,PRIMARY KEY(a,c)) WITHOUT ROWID);
CREATE TABLE t1(a,b,c,d,PRIMARY KEY(a,c,a,c)) WITHOUT ROWID);
CREATE TABLE t1(a,b,c,d,PRIMARY KEY(a,A,a,C)) WITHOUT ROWID);
CREATE TABLE t1(a,b,c,d,PRIMARY KEY(a,a,a,a,c)) WITHOUT ROWID);
</pre></blockquote>)^

<p>The first example above is the preferred definition of the table,
of course.  ^All of the examples create a WITHOUT ROWID table with
two PRIMARY KEY columns, "a" and "c", in that order, followed by
two data columns "b" and "d", also in that order.








|
|
|
|







1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
<p>^If the PRIMARY KEY of a WITHOUT ROWID tables uses the same columns
with the same collating sequence more than once, then the second and
subsequent occurrences of that column in the PRIMARY KEY definition are
ignored.  ^(For example, the following CREATE TABLE statements all specify
the same table, which will have the exact same representation on disk:

<blockquote><pre>
CREATE TABLE t1(a,b,c,d,PRIMARY KEY(a,c)) WITHOUT ROWID;
CREATE TABLE t1(a,b,c,d,PRIMARY KEY(a,c,a,c)) WITHOUT ROWID;
CREATE TABLE t1(a,b,c,d,PRIMARY KEY(a,A,a,C)) WITHOUT ROWID;
CREATE TABLE t1(a,b,c,d,PRIMARY KEY(a,a,a,a,c)) WITHOUT ROWID;
</pre></blockquote>)^

<p>The first example above is the preferred definition of the table,
of course.  ^All of the examples create a WITHOUT ROWID table with
two PRIMARY KEY columns, "a" and "c", in that order, followed by
two data columns "b" and "d", also in that order.