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

Commitd014e6c

Browse files
committed
Clarify the result order of unnest(multirange).
It is best not to mention the storage order, because that isan implementation detail and has confused at least one user,who assumed that the storage order is the order in which theconstituent ranges were written in SQL.Since the sorting order is explained at the beginning of thepage, it should be sufficient to say that the ranges arereturned in ascending order.Author: Laurenz AlbeReviewed-by: Daniel FredouilleDiscussion:https://postgr.es/m/169627213477.3727338.17653654241633692682%40wrigleys.postgresql.org
1 parent12cf3ac commitd014e6c

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

‎doc/src/sgml/func.sgml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20218,8 +20218,7 @@ SELECT NULLIF(value, '(none)') ...
2021820218
<returnvalue>setof anyrange</returnvalue>
2021920219
</para>
2022020220
<para>
20221-
Expands a multirange into a set of ranges.
20222-
The ranges are read out in storage order (ascending).
20221+
Expands a multirange into a set of ranges in ascending order.
2022320222
</para>
2022420223
<para>
2022520224
<literal>unnest('{[1,2), [3,4)}'::int4multirange)</literal>

0 commit comments

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