1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Using Sequences</title>
<link rel="stylesheet" href="gettingStarted.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
<link rel="start" href="index.html" title="Getting Started with the Oracle Berkeley DB SQL APIs" />
<link rel="up" href="dbsqlbasics.html" title="Chapter 1. Berkeley DB SQL: The Absolute Basics" />
<link rel="prev" href="sql_encryption.html" title="Encryption" />
<link rel="next" href="normal-sql.html" title="Differences for Users of other SQL Engines" />
</head>
<body>
<div xmlns="" class="navheader">
<div class="libver">
<p>Library Version 11.2.5.3</p>
</div>
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Using Sequences</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="sql_encryption.html">Prev</a> </td>
<th width="60%" align="center">Chapter 1. Berkeley DB SQL: The Absolute Basics</th>
<td width="20%" align="right"> <a accesskey="n" href="normal-sql.html">Next</a></td>
</tr>
</table>
<hr />
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a id="sequencesupport"></a>Using Sequences</h2>
</div>
</div>
</div>
<div class="toc">
<dl>
<dt>
<span class="sect2">
<a href="sequencesupport.html#create_sequence">create_sequence</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="sequencesupport.html#seq_nextval">nextval</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="sequencesupport.html#seq_currval">currval</a>
</span>
</dt>
<dt>
<span class="sect2">
<a href="sequencesupport.html#seq_drop_sequence">drop_sequence</a>
</span>
</dt>
</dl>
</div>
<p>
You can use sequences with the SQL API.
Sequences provide for an arbitrary number of increasing or
decreasing integers that persist across database accesses.
Use sequences if you need to create unique values in a
highly efficient and persistent way.
</p>
<p>
To create and access a sequence, you must use SQL
functionality that is unique to the BDB SQL interface; no
corresponding functionality exists in SQLite. The
sequence functionality is implemented using SQLite
function plugins, as such it is necessary to use the
'select' keyword as a prefix to all sequence APIs.
</p>
<p>
The SQL API sequence support is a partial implementation of
the sequence API defined in the SQL 2003 specification.
</p>
<p>
The following sections describe the BDB SQL interface sequence API.
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="create_sequence"></a>create_sequence</h3>
</div>
</div>
</div>
<p>
Creates a new sequence. A name is required, all other
parameters are optional. For example:
</p>
<pre class="programlisting">SELECT create_sequence("my_sequence", "start", 100, "incr", 10,
"maxvalue", 300);</pre>
<p>
This creates a sequence called <code class="literal">my_sequence</code>
starting at 100 and incrementing by 10 until it reaches
300.
</p>
<pre class="programlisting">SELECT create_sequence("my_decr_sequence", "incr", -100,
"minvalue", -10000);</pre>
<p>
This creates a sequence call <code class="literal">my_decr_sequence</code>
starting at 0 and decreasing by 100 until it reaches
-10000.
</p>
<p>
Parameters are:
</p>
<div class="itemizedlist">
<ul type="disc">
<li>
<p>
<code class="literal">name</code>
</p>
<p>
Required parameter that provides the name of
the sequence. It is an error to create a
sequence with another name that is currently in
use within the database.
</p>
</li>
<li>
<p>
<code class="literal">start</code>
</p>
<p>
The starting value for the sequence. If this
parameter is not provided then
<code class="literal">0</code> is used.
</p>
</li>
<li>
<p>
<code class="literal">minvalue</code>
</p>
<p>
The lowest value generated by the sequence. If
this parameter is not provided and a
decrementing sequence is created, then
INT64_MIN is used.
</p>
</li>
<li>
<p>
<code class="literal">maxvalue</code>
</p>
<p>
The largest value generated by the sequence.
If this parameter is not provided and an
incrementing sequence is created, then
INT64_MAX is used.
</p>
</li>
<li>
<p>
<code class="literal">incr</code>
</p>
<p>
The amount the sequence is incremented for each
get operation. This value can be positive or
negative. If this parameter is not provided,
then <code class="literal">1</code> is used.
</p>
</li>
<li>
<p>
<code class="literal">cache</code>
</p>
<p>
Causes each handle to keep a cache of sequence
values. So long as there are values available
in the cache, retrieving the next value is
cheap and does not lead to contention between
handles.
</p>
<p>
Sequences with caches cannot be created or dropped
within an explicit transaction.
</p>
<p>
Operations on caching sequences are not
transactionally protected. That is, a rollback
will not result in a value being returned to
the sequence.
</p>
<p>
Sequences with caches do not support the
<code class="literal">currval</code> function.
</p>
<p>
The parameter following the cache parameter must be
an integer value specifying the size of the cache.
</p>
</li>
</ul>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="seq_nextval"></a>nextval</h3>
</div>
</div>
</div>
<p>
Retrieves the next value from the named sequence. For
example:
</p>
<pre class="programlisting">SELECT nextval("my_sequence");</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="seq_currval"></a>currval</h3>
</div>
</div>
</div>
<p>
Retrieves the last value that was returned from the
named sequence. For example:
</p>
<pre class="programlisting">SELECT currval("my_sequence");</pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="seq_drop_sequence"></a>drop_sequence</h3>
</div>
</div>
</div>
<p>
Removes the sequence. For example:
</p>
<pre class="programlisting">SELECT drop_sequence("my_sequence");</pre>
</div>
</div>
<div class="navfooter">
<hr />
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="sql_encryption.html">Prev</a> </td>
<td width="20%" align="center">
<a accesskey="u" href="dbsqlbasics.html">Up</a>
</td>
<td width="40%" align="right"> <a accesskey="n" href="normal-sql.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Encryption </td>
<td width="20%" align="center">
<a accesskey="h" href="index.html">Home</a>
</td>
<td width="40%" align="right" valign="top"> Differences for Users of other SQL Engines</td>
</tr>
</table>
</div>
</body>
</html>
|