3
PostgreSQL documentation
6
<refentry id="SQL-DECLARE">
8
<refentrytitle id="SQL-DECLARE-TITLE">DECLARE</refentrytitle>
9
<manvolnum>7</manvolnum>
10
<refmiscinfo>SQL - Language Statements</refmiscinfo>
14
<refname>DECLARE</refname>
15
<refpurpose>define a cursor</refpurpose>
18
<indexterm zone="sql-declare">
19
<primary>DECLARE</primary>
22
<indexterm zone="sql-declare">
23
<primary>cursor</primary>
24
<secondary>DECLARE</secondary>
29
DECLARE <replaceable class="parameter">name</replaceable> [ BINARY ] [ INSENSITIVE ] [ [ NO ] SCROLL ]
30
CURSOR [ { WITH | WITHOUT } HOLD ] FOR <replaceable class="parameter">query</replaceable>
35
<title>Description</title>
38
<command>DECLARE</command> allows a user to create cursors, which
39
can be used to retrieve
40
a small number of rows at a time out of a larger query.
41
After the cursor is created, rows are fetched from it using
42
<xref linkend="sql-fetch" endterm="sql-fetch-title">.
47
<title>Parameters</title>
51
<term><replaceable class="parameter">name</replaceable></term>
54
The name of the cursor to be created.
60
<term><literal>BINARY</literal></term>
63
Causes the cursor to return data in binary rather than in text format.
69
<term><literal>INSENSITIVE</literal></term>
72
Indicates that data retrieved from the cursor should be
73
unaffected by updates to the table(s) underlying the cursor that occur
74
after the cursor is created. In <productname>PostgreSQL</productname>,
75
this is the default behavior; so this key word has no
76
effect and is only accepted for compatibility with the SQL standard.
82
<term><literal>SCROLL</literal></term>
83
<term><literal>NO SCROLL</literal></term>
86
<literal>SCROLL</literal> specifies that the cursor can be used
87
to retrieve rows in a nonsequential fashion (e.g.,
88
backward). Depending upon the complexity of the query's
89
execution plan, specifying <literal>SCROLL</literal> might impose
90
a performance penalty on the query's execution time.
91
<literal>NO SCROLL</literal> specifies that the cursor cannot be
92
used to retrieve rows in a nonsequential fashion. The default is to
93
allow scrolling in some cases; this is not the same as specifying
94
<literal>SCROLL</literal>. See <xref linkend="sql-declare-notes"
95
endterm="sql-declare-notes-title"> for details.
101
<term><literal>WITH HOLD</literal></term>
102
<term><literal>WITHOUT HOLD</literal></term>
105
<literal>WITH HOLD</literal> specifies that the cursor can
106
continue to be used after the transaction that created it
107
successfully commits. <literal>WITHOUT HOLD</literal> specifies
108
that the cursor cannot be used outside of the transaction that
109
created it. If neither <literal>WITHOUT HOLD</literal> nor
110
<literal>WITH HOLD</literal> is specified, <literal>WITHOUT
111
HOLD</literal> is the default.
117
<term><replaceable class="parameter">query</replaceable></term>
120
A <xref linkend="sql-select" endterm="sql-select-title"> or
121
<xref linkend="sql-values" endterm="sql-values-title"> command
122
which will provide the rows to be returned by the cursor.
129
The key words <literal>BINARY</literal>,
130
<literal>INSENSITIVE</literal>, and <literal>SCROLL</literal> can
135
<refsect1 id="sql-declare-notes">
136
<title id="sql-declare-notes-title">Notes</title>
139
Normal cursors return data in text format, the same as a
140
<command>SELECT</> would produce. The <literal>BINARY</> option
141
specifies that the cursor should return data in binary format.
142
This reduces conversion effort for both the server and client,
143
at the cost of more programmer effort to deal with platform-dependent
145
As an example, if a query returns a value of one from an integer column,
146
you would get a string of <literal>1</> with a default cursor,
147
whereas with a binary cursor you would get
148
a 4-byte field containing the internal representation of the value
149
(in big-endian byte order).
153
Binary cursors should be used carefully. Many applications,
154
including <application>psql</application>, are not prepared to
155
handle binary cursors and expect data to come back in the text
161
When the client application uses the <quote>extended query</> protocol
162
to issue a <command>FETCH</> command, the Bind protocol message
163
specifies whether data is to be retrieved in text or binary format.
164
This choice overrides the way that the cursor is defined. The concept
165
of a binary cursor as such is thus obsolete when using extended query
166
protocol — any cursor can be treated as either text or binary.
171
Unless <literal>WITH HOLD</literal> is specified, the cursor
172
created by this command can only be used within the current
173
transaction. Thus, <command>DECLARE</> without <literal>WITH
174
HOLD</literal> is useless outside a transaction block: the cursor would
175
survive only to the completion of the statement. Therefore
176
<productname>PostgreSQL</productname> reports an error if such a
177
command is used outside a transaction block.
179
<xref linkend="sql-begin" endterm="sql-begin-title"> and
180
<xref linkend="sql-commit" endterm="sql-commit-title">
181
(or <xref linkend="sql-rollback" endterm="sql-rollback-title">)
182
to define a transaction block.
186
If <literal>WITH HOLD</literal> is specified and the transaction
187
that created the cursor successfully commits, the cursor can
188
continue to be accessed by subsequent transactions in the same
189
session. (But if the creating transaction is aborted, the cursor
190
is removed.) A cursor created with <literal>WITH HOLD</literal>
191
is closed when an explicit <command>CLOSE</command> command is
192
issued on it, or the session ends. In the current implementation,
193
the rows represented by a held cursor are copied into a temporary
194
file or memory area so that they remain available for subsequent
199
<literal>WITH HOLD</literal> may not be specified when the query
200
includes <literal>FOR UPDATE</> or <literal>FOR SHARE</>.
204
The <literal>SCROLL</> option should be specified when defining a
205
cursor that will be used to fetch backwards. This is required by
206
the SQL standard. However, for compatibility with earlier
207
versions, <productname>PostgreSQL</productname> will allow
208
backward fetches without <literal>SCROLL</>, if the cursor's query
209
plan is simple enough that no extra overhead is needed to support
210
it. However, application developers are advised not to rely on
211
using backward fetches from a cursor that has not been created
212
with <literal>SCROLL</literal>. If <literal>NO SCROLL</> is
213
specified, then backward fetches are disallowed in any case.
217
Backward fetches are also disallowed when the query
218
includes <literal>FOR UPDATE</> or <literal>FOR SHARE</>; therefore
219
<literal>SCROLL</literal> may not be specified in this case.
223
If the cursor's query includes <literal>FOR UPDATE</> or <literal>FOR
224
SHARE</>, then returned rows are locked at the time they are first
225
fetched, in the same way as for a regular
226
<xref linkend="sql-select" endterm="sql-select-title"> command with
228
In addition, the returned rows will be the most up-to-date versions;
229
therefore these options provide the equivalent of what the SQL standard
230
calls a <quote>sensitive cursor</>. (Specifying <literal>INSENSITIVE</>
231
together with <literal>FOR UPDATE</> or <literal>FOR SHARE</> is an error.)
236
It is generally recommended to use <literal>FOR UPDATE</> if the cursor
237
is intended to be used with <command>UPDATE ... WHERE CURRENT OF</> or
238
<command>DELETE ... WHERE CURRENT OF</>. Using <literal>FOR UPDATE</>
239
prevents other sessions from changing the rows between the time they are
240
fetched and the time they are updated. Without <literal>FOR UPDATE</>,
241
a subsequent <literal>WHERE CURRENT OF</> command will have no effect if
242
the row was changed since the cursor was created.
246
Another reason to use <literal>FOR UPDATE</> is that without it, a
247
subsequent <literal>WHERE CURRENT OF</> might fail if the cursor query
248
does not meet the SQL standard's rules for being <quote>simply
249
updatable</> (in particular, the cursor must reference just one table
250
and not use grouping or <literal>ORDER BY</>). Cursors
251
that are not simply updatable might work, or might not, depending on plan
252
choice details; so in the worst case, an application might work in testing
253
and then fail in production.
257
The main reason not to use <literal>FOR UPDATE</> with <literal>WHERE
258
CURRENT OF</> is if you need the cursor to be scrollable, or to be
259
insensitive to the subsequent updates (that is, continue to show the old
260
data). If this is a requirement, pay close heed to the caveats shown
266
The SQL standard only makes provisions for cursors in embedded
267
<acronym>SQL</acronym>. The <productname>PostgreSQL</productname>
268
server does not implement an <command>OPEN</command> statement for
269
cursors; a cursor is considered to be open when it is declared.
270
However, <application>ECPG</application>, the embedded SQL
271
preprocessor for <productname>PostgreSQL</productname>, supports
272
the standard SQL cursor conventions, including those involving
273
<command>DECLARE</command> and <command>OPEN</command> statements.
277
You can see all available cursors by querying the <link
278
linkend="view-pg-cursors"><structname>pg_cursors</structname></link>
284
<title>Examples</title>
289
DECLARE liahona CURSOR FOR SELECT * FROM films;
291
See <xref linkend="sql-fetch" endterm="sql-fetch-title"> for more
292
examples of cursor usage.
297
<title>Compatibility</title>
300
The SQL standard says that it is implementation-dependent whether cursors
301
are sensitive to concurrent updates of the underlying data by default. In
302
<productname>PostgreSQL</productname>, cursors are insensitive by default,
303
and can be made sensitive by specifying <literal>FOR UPDATE</>. Other
304
products may work differently.
308
The SQL standard allows cursors only in embedded
309
<acronym>SQL</acronym> and in modules. <productname>PostgreSQL</>
310
permits cursors to be used interactively.
314
Binary cursors are a <productname>PostgreSQL</productname>
320
<title>See Also</title>
322
<simplelist type="inline">
323
<member><xref linkend="sql-close" endterm="sql-close-title"></member>
324
<member><xref linkend="sql-fetch" endterm="sql-fetch-title"></member>
325
<member><xref linkend="sql-move" endterm="sql-move-title"></member>