pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Unordered SELECT - random vs undefined
4+ messages / 2 participants
[nested] [flat]

* Unordered SELECT - random vs undefined
@ 2010-08-20 13:35 Thom Brown <thom@linux.com>
  2010-08-20 13:45 ` Re: Unordered SELECT - random vs undefined Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 4+ messages in thread

From: Thom Brown @ 2010-08-20 13:35 UTC (permalink / raw)
  To: pgsql-docs

Keith Gabryelski submitted this comment for the docs, which I rejected
as a comment, but think still needs correcting in the docs:

the line:
When a table is read, the rows will appear in random order, unless
sorting is explicitly requested

should be:
When a table is read, the rows will appear in an undefined order,
unless sorting is explicitly requested.

This applies to: http://www.postgresql.org/docs/current/static/ddl-basics.html


-- 
Thom Brown
Registered Linux user: #516935



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Unordered SELECT - random vs undefined
  2010-08-20 13:35 Unordered SELECT - random vs undefined Thom Brown <thom@linux.com>
@ 2010-08-20 13:45 ` Tom Lane <tgl@sss.pgh.pa.us>
  2010-08-20 13:49   ` Re: Unordered SELECT - random vs undefined Thom Brown <thom@linux.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Tom Lane @ 2010-08-20 13:45 UTC (permalink / raw)
  To: Thom Brown <thom@linux.com>; +Cc: pgsql-docs

Thom Brown <thom@linux.com> writes:
> should be:
> When a table is read, the rows will appear in an undefined order,
> unless sorting is explicitly requested.

Perhaps "unspecified" is le mot juste.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Unordered SELECT - random vs undefined
  2010-08-20 13:35 Unordered SELECT - random vs undefined Thom Brown <thom@linux.com>
  2010-08-20 13:45 ` Re: Unordered SELECT - random vs undefined Tom Lane <tgl@sss.pgh.pa.us>
@ 2010-08-20 13:49   ` Thom Brown <thom@linux.com>
  2010-08-20 14:01     ` Re: Unordered SELECT - random vs undefined Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 4+ messages in thread

From: Thom Brown @ 2010-08-20 13:49 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-docs

On 20 August 2010 14:45, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thom Brown <thom@linux.com> writes:
>> should be:
>> When a table is read, the rows will appear in an undefined order,
>> unless sorting is explicitly requested.
>
> Perhaps "unspecified" is le mot juste.
>

Yes, that sounds more appopriate.

-- 
Thom Brown
Registered Linux user: #516935



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Unordered SELECT - random vs undefined
  2010-08-20 13:35 Unordered SELECT - random vs undefined Thom Brown <thom@linux.com>
  2010-08-20 13:45 ` Re: Unordered SELECT - random vs undefined Tom Lane <tgl@sss.pgh.pa.us>
  2010-08-20 13:49   ` Re: Unordered SELECT - random vs undefined Thom Brown <thom@linux.com>
@ 2010-08-20 14:01     ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 4+ messages in thread

From: Tom Lane @ 2010-08-20 14:01 UTC (permalink / raw)
  To: Thom Brown <thom@linux.com>; +Cc: pgsql-docs

Thom Brown <thom@linux.com> writes:
> On 20 August 2010 14:45, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Perhaps "unspecified" is le mot juste.

> Yes, that sounds more appopriate.

OK, done.  I found one other place in the docs where "random" seemed
to be used inappropriately, too.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2010-08-20 14:01 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-08-20 13:35 Unordered SELECT - random vs undefined Thom Brown <thom@linux.com>
2010-08-20 13:45 ` Tom Lane <tgl@sss.pgh.pa.us>
2010-08-20 13:49   ` Thom Brown <thom@linux.com>
2010-08-20 14:01     ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox