>No, we don't have any concept of member functions. Just create the
>composite type (I'm assuming it needs to be composite) and then create
>functions that take it as parameter.
>
>Note that because PG allows function overloading, there's no conflict
>between, say, to_string(D_Temp_Element) a
Ben Ali Rachid writes:
> I've a Oracle type that I must translate to Postgres. This Oracle type is
> like below :
> CREATE OR REPLACE
> type D_Temp_Element as object
> (
> MEMBER FUNCTION to_string return Varchar2,
> MEMBER FUNCTION duration return D_Interval,
> ...
> ) ;
> How can I d
