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

Commitd99e7b5

Browse files
committed
Add note explaining that a mergejoinable equality operator is now
required if a datatype is to be accepted by GROUP BY, DISTINCT, orORDER BY. This is documentation for code changes made pursuant topgsql-hackers discussion around 29-Nov-02.
1 parentdaec989 commitd99e7b5

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

‎doc/src/sgml/xoper.sgml

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/xoper.sgml,v 1.20 2002/09/21 18:32:54 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/xoper.sgml,v 1.21 2003/01/06 01:20:40 tgl Exp $
33
-->
44

55
<Chapter Id="xoper">
@@ -472,6 +472,17 @@ table1.column1 OP table2.column2
472472
</itemizedlist>
473473
</para>
474474

475+
<note>
476+
<para>
477+
<literal>GROUP BY</> and <literal>DISTINCT</> operations require each
478+
datatype being grouped or compared to have a mergejoinable
479+
equality operator named <literal>=</>. The equality operator and its
480+
associated <literal>SORT1</> operator are used to implement these
481+
operations. Also, the associated <literal>SORT1</> operator is the
482+
default ordering operator for <literal>ORDER BY</>.
483+
</para>
484+
</note>
485+
475486
<note>
476487
<para>
477488
In <ProductName>PostgreSQL</ProductName> versions before 7.3,

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp