|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.6 2000/05/1619:29:43 momjian Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.7 2000/05/1621:16:12 momjian Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <chapter> |
@@ -299,7 +299,7 @@ RENAME <replaceable>oldname</replaceable> TO <replaceable>newname</replaceable>; |
299 | 299 | <para> |
300 | 300 | Using the <replaceable>class.field</replaceable>%TYPE |
301 | 301 | causes PL/pgSQL to lookup the attributes definitions at the |
302 | | - first call to thefunciton during the lifetime of a backend. |
| 302 | + first call to thefunction during the lifetime of a backend. |
303 | 303 | Have a table with a char(20) attribute and some PL/pgSQL functions |
304 | 304 | that deal with it's content in local variables. Now someone |
305 | 305 | decides that char(20) isn't enough, dumps the table, drops it, |
|