summaryrefslogtreecommitdiff
path: root/doc/src/sgml/ref/create_cast.sgml
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2014-02-24 12:56:37 -0500
committerBruce Momjian <bruce@momjian.us>2014-02-24 12:56:37 -0500
commit6f14a6f703a26ec12f4da6f53f107dd260fbb9db (patch)
tree1fd0ef96989e3672dcd50ca6966283c7ca8ad8c4 /doc/src/sgml/ref/create_cast.sgml
parent4bad548d981636ceb79492a1b7f607f22f0867de (diff)
docs: remove unnecessary references to old PG versions
Diffstat (limited to 'doc/src/sgml/ref/create_cast.sgml')
-rw-r--r--doc/src/sgml/ref/create_cast.sgml11
1 files changed, 0 insertions, 11 deletions
diff --git a/doc/src/sgml/ref/create_cast.sgml b/doc/src/sgml/ref/create_cast.sgml
index 2e69a10a8ef..11266755e56 100644
--- a/doc/src/sgml/ref/create_cast.sgml
+++ b/doc/src/sgml/ref/create_cast.sgml
@@ -332,17 +332,6 @@ SELECT CAST ( 2 AS numeric ) + 4.0;
</para>
<para>
- Prior to <productname>PostgreSQL</> 7.3, every function that had
- the same name as a data type, returned that data type, and took one
- argument of a different type was automatically a cast function.
- This convention has been abandoned in face of the introduction of
- schemas and to be able to represent binary-coercible casts in the
- system catalogs. The built-in cast functions still follow this naming
- scheme, but they have to be shown as casts in the system catalog
- <structname>pg_cast</> as well.
- </para>
-
- <para>
While not required, it is recommended that you continue to follow this old
convention of naming cast implementation functions after the target data
type. Many users are used to being able to cast data types using a