Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitc3d2b49

Browse files
committed
datatype -> data type.
1 parent39ee0f5 commitc3d2b49

File tree

4 files changed

+19
-19
lines changed

4 files changed

+19
-19
lines changed

‎doc/src/sgml/ref/create_aggregate.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.10 2000/07/17 03:04:41 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.11 2000/09/12 20:52:07 momjian Exp $
33
Postgres documentation
44
-->
55

@@ -98,7 +98,7 @@ CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> ( BASETYPE =
9898
result after all input data has been traversed. The function
9999
must take a single argument of type
100100
<replaceable class="PARAMETER">state_type</replaceable>.
101-
The outputdatatype of the aggregate is defined as the return
101+
The outputdata type of the aggregate is defined as the return
102102
type of this function.
103103
If <replaceable class="PARAMETER">ffunc</replaceable>
104104
is not specified, then the ending state value is used as the
@@ -113,7 +113,7 @@ CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> ( BASETYPE =
113113
<listitem>
114114
<para>
115115
The initial setting for the state value. This must be a literal
116-
constant in the form accepted for thedatatype
116+
constant in the form accepted for thedata type
117117
<replaceable class="PARAMETER">state_type</replaceable>.
118118
If not specified, the state value starts out NULL.
119119
</para>
@@ -201,7 +201,7 @@ CREATE
201201
that is, an initial value for the internal state value.
202202
This is specified and stored in the database as a field of type
203203
<type>text</type>, but it must be a valid external representation
204-
of a constant of the state valuedatatype. If it is not supplied
204+
of a constant of the state valuedata type. If it is not supplied
205205
then the state value starts out NULL.
206206
</para>
207207

‎doc/src/sgml/ref/create_index.sgml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.14 2000/06/19 03:54:15 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.15 2000/09/12 20:52:08 momjian Exp $
33
Postgres documentation
44
-->
55

@@ -290,11 +290,11 @@ ERROR: Cannot create index: 'index_name' already exists.
290290
four-byte integers would use the <literal>int4_ops</literal> class;
291291
this operator class includes comparison functions for four-byte
292292
integers. In practice the default operator class for the field's
293-
datatype is usually sufficient. The main point of having operator classes
294-
is that for somedatatypes, there could be more than one meaningful
295-
ordering. For example, we might want to sort a complex-numberdatatype
293+
data type is usually sufficient. The main point of having operator classes
294+
is that for somedata types, there could be more than one meaningful
295+
ordering. For example, we might want to sort a complex-numberdata type
296296
either by absolute value or by real part. We could do this by defining
297-
two operator classes for thedatatype and then selecting the proper
297+
two operator classes for thedata type and then selecting the proper
298298
class when making an index. There are also some operator classes with
299299
special purposes:
300300

@@ -303,7 +303,7 @@ ERROR: Cannot create index: 'index_name' already exists.
303303
<para>
304304
The operator classes <literal>box_ops</literal> and
305305
<literal>bigbox_ops</literal> both support rtree indices on the
306-
<literal>box</literal>datatype.
306+
<literal>box</literal>data type.
307307
The difference between them is that <literal>bigbox_ops</literal>
308308
scales box coordinates down, to avoid floating point exceptions from
309309
doing multiplication, addition, and subtraction on very large

‎doc/src/sgml/ref/create_operator.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.15 2000/08/1205:15:23 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.16 2000/09/1220:52:08 momjian Exp $
33
Postgres documentation
44
-->
55

@@ -303,8 +303,8 @@ MYBOXES.description !== box '((0,0),(1,1))'
303303
the lines of [SHAP86]; however, it must know whether this
304304
strategy is applicable. The current hash-join algorithm
305305
is only correct for operators that represent equality tests;
306-
furthermore, equality of thedatatype must mean bitwise equality
307-
of the representation of the type. (For example, adatatype that
306+
furthermore, equality of thedata type must mean bitwise equality
307+
of the representation of the type. (For example, adata type that
308308
contains unused bits that don't matter for equality tests could
309309
not be hashjoined.)
310310
The HASHES flag indicates to the query optimizer that a hash join

‎doc/src/sgml/ref/create_type.sgml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.13 2000/08/24 23:36:29 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.14 2000/09/12 20:52:08 momjian Exp $
33
Postgres documentation
44
-->
55

@@ -122,7 +122,7 @@ CREATE TYPE <replaceable class="parameter">typename</replaceable> ( INPUT = <rep
122122
<term><replaceable class="parameter">default</replaceable></term>
123123
<listitem>
124124
<para>
125-
The default value for thedatatype. Usually this is omitted,
125+
The default value for thedata type. Usually this is omitted,
126126
so that the default is NULL.
127127
</para>
128128
</listitem>
@@ -152,7 +152,7 @@ CREATE TYPE <replaceable class="parameter">typename</replaceable> ( INPUT = <rep
152152
<term><replaceable class="parameter">alignment</replaceable></term>
153153
<listitem>
154154
<para>
155-
Storage alignment requirement of thedatatype. If specified, must
155+
Storage alignment requirement of thedata type. If specified, must
156156
be '<literal>int4</literal>' or '<literal>double</literal>';
157157
the default is '<literal>int4</literal>'.
158158
</para>
@@ -163,7 +163,7 @@ CREATE TYPE <replaceable class="parameter">typename</replaceable> ( INPUT = <rep
163163
<term><replaceable class="parameter">storage</replaceable></term>
164164
<listitem>
165165
<para>
166-
Storage technique for thedatatype. If specified, must
166+
Storage technique for thedata type. If specified, must
167167
be '<literal>plain</literal>', '<literal>external</literal>',
168168
'<literal>extended</literal>', or '<literal>main</literal>';
169169
the default is '<literal>plain</literal>'.
@@ -298,9 +298,9 @@ CREATE
298298

299299
<para>
300300
The <replaceable class="parameter">storage</replaceable> keyword
301-
allows selection of TOAST storage method for variable-lengthdatatypes
301+
allows selection of TOAST storage method for variable-lengthdata types
302302
(only <literal>plain</literal> is allowed for fixed-length types).
303-
<literal>plain</literal> disables TOAST for thedatatype: it will always
303+
<literal>plain</literal> disables TOAST for thedata type: it will always
304304
be stored in-line and not compressed.
305305
<literal>extended</literal> is full TOAST capability: the system will
306306
first try to compress a long data value, and will move the value out of

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp