Re: Oracle to Postgres : create type as object in Postgres

From: Ben Ali Rachid <souliman239(at)yahoo(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Oracle to Postgres : create type as object in Postgres
Date: 2009-05-24 20:03:27
Message-ID: 467825.91042.qm@web28514.mail.ukl.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>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) and to_string(Some_Other_Type).

>If you were only using member functions to prevent that kind of

>conflict, I don't think you need to worry too much.

OK thanks.

>PS: this is not an appropriate question for -hackers.  Please direct

>simple usage questions to -general in future.

Sorry.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-05-24 20:05:18 Re: generic options for explain
Previous Message Tom Lane 2009-05-24 19:09:54 Re: generic options for explain