|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.31 2003/11/3004:47:37 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.32 2003/11/3005:45:22 momjian Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <chapter id="plpgsql"> |
@@ -957,11 +957,8 @@ SELECT INTO <replaceable>target</replaceable> <replaceable>select_expressions</r |
957 | 957 | </para> |
958 | 958 |
|
959 | 959 | <para> |
960 | | - At present, the <literal>INTO</> clause can appear almost anywhere in the <command>SELECT</command> |
961 | | - statement, but it is recommended to place it immediately after the <literal>SELECT</literal> |
962 | | - key word as depicted above. Future versions of |
963 | | - <application>PL/pgSQL</application> may be less forgiving about |
964 | | - placement of the <literal>INTO</literal> clause. |
| 960 | + The <literal>INTO</> clause can appear almost anywhere in the <command>SELECT</command> |
| 961 | + statement. |
965 | 962 | </para> |
966 | 963 |
|
967 | 964 | <para> |
|