Add a bunch of pseudo-types to replace the behavior formerly associated

with OPAQUE, as per recent pghackers discussion.  I still want to do some
more work on the 'cstring' pseudo-type, but I'm going to commit the bulk
of the changes now before the tree starts shifting under me ...

1 files changed, 4 insertions, 5 deletions

diff --git a/src/tutorial/complex.source b/src/tutorial/complex.source
index 5df3c5d6779..382eea25e9f 100644
--- a/src/tutorial/complex.source
+++ b/src/tutorial/complex.source
@@ -8,7 +8,7 @@
 -- Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group
 -- Portions Copyright (c) 1994, Regents of the University of California
 --
--- $Header: /cvsroot/pgsql/src/tutorial/complex.source,v 1.13 2002/07/30 05:24:56 tgl Exp $
+-- $Header: /cvsroot/pgsql/src/tutorial/complex.source,v 1.14 2002/08/22 00:01:51 tgl Exp $
 --
 ---------------------------------------------------------------------------
 
@@ -28,7 +28,7 @@
 -- (in memory) representation. You will get a message telling you 'complex'
 -- does not exist yet but that's okay.
 
-CREATE FUNCTION complex_in(opaque)
+CREATE FUNCTION complex_in(cstring)
    RETURNS complex
    AS '_OBJWD_/complex'
    LANGUAGE 'c';
@@ -36,8 +36,8 @@ CREATE FUNCTION complex_in(opaque)
 -- the output function 'complex_out' takes the internal representation and
 -- converts it into the textual representation.
 
-CREATE FUNCTION complex_out(opaque)
-   RETURNS opaque
+CREATE FUNCTION complex_out(complex)
+   RETURNS cstring
    AS '_OBJWD_/complex'
    LANGUAGE 'c';
 
@@ -195,4 +195,3 @@ SELECT * from test_complex where a > '(56.0,-22.5)';
 -- clean up the example
 DROP TABLE test_complex;
 DROP TYPE complex CASCADE;
-DROP FUNCTION complex_out(opaque);