From da1eacb8d2cebc5b43bbe2c93f1c74c962182ae5 Mon Sep 17 00:00:00 2001
From: Tom Lane
Date: Thu, 1 Dec 2011 16:39:07 -0500
Subject: Clarify documentation about SQL:2008 variant of LIMIT/OFFSET syntax.
The point that you need parentheses for non-constant expressions apparently
needs to be brought out a bit more clearly, per bug #6315.
---
doc/src/sgml/ref/select.sgml | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index 15d9b75b59b..3fbfda309e2 100644
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -1056,17 +1056,19 @@ OFFSET start
OFFSET start { ROW | ROWS }
FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY
- According to the standard, the OFFSET clause must come
- before the FETCH clause if both are present; but
- PostgreSQL is laxer and allows either order.
+ In this syntax, to write anything except a simple integer constant for
+ start or count, you must write parentheses
+ around it.
+ If count is
+ omitted in a FETCH clause, it defaults to 1.
ROW
and ROWS as well as FIRST
and NEXT are noise words that don't influence
- the effects of these clauses. In this syntax, when using expressions
- other than simple constants for start
- or count, parentheses will be
- necessary in most cases. If count is
- omitted in FETCH, it defaults to 1.
+ the effects of these clauses.
+ According to the standard, the OFFSET clause must come
+ before the FETCH clause if both are present; but
+ PostgreSQL is laxer and allows either order.
--
cgit v1.2.3