|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.11 2000/12/25 23:15:26 petere Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.12 2001/02/15 21:11:17 tgl Exp $ |
3 | 3 | Postgres documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -166,7 +166,7 @@ NOTICE: Closing pre-existing portal "<replaceable class="parameter">cursorname< |
166 | 166 |
|
167 | 167 | <varlistentry> |
168 | 168 | <term><computeroutput> |
169 | | -ERROR:Named portals may only be used in begin/end transaction blocks |
| 169 | +ERROR:DECLARE CURSOR may only be used in begin/end transaction blocks |
170 | 170 | </computeroutput></term> |
171 | 171 | <listitem> |
172 | 172 | <para> |
@@ -223,8 +223,8 @@ ERROR: Named portals may only be used in begin/end transaction blocks |
223 | 223 |
|
224 | 224 | <para> |
225 | 225 | String representation is architecture-neutral whereas binary |
226 | | - representation can differ between different machine architectures |
227 | | -and<emphasis><productname>Postgres</productname> does not resolve |
| 226 | + representation can differ between different machine architectures. |
| 227 | + <emphasis><productname>Postgres</productname> does not resolve |
228 | 228 | byte ordering or representation issues for binary cursors</emphasis>. |
229 | 229 | Therefore, if your client machine and server machine use different |
230 | 230 | representations (e.g., "big-endian" versus "little-endian"), |
|