| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Ramesh T <rameshparnanditech(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: tab_to_sting |
| Date: | 2014-07-23 20:41:42 |
| Message-ID: | 53D01E06.5080606@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 07/23/2014 09:12 AM, Ramesh T wrote:
> Hi,
>
> SELECT hr.tab_to_largestring(CAST(COLLECT(cust_name) AS
> t_varchar2_tab)) AS employees
> FROM hr.customer
>
> when i run function for table column values to single row function
> name is hr.tab_to_largestring
>
> this code from oracle
>
> it return like function collect(character varying) does not exit
>
> please let me know in postgres collect () key is thier..?
>
>
> and how to run this function..?
To help with getting answers, it would be helpful if you told the list
what the Oracle function does or point to the documentation:
http://docs.oracle.com/cd/E11882_01/server.112/e26088/functions031.htm#SQLRF51285
Another option would be to investigate EnterpriseDB as they have an
Oracle compatibility layer available:
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seamus Abshere | 2014-07-23 20:45:50 | Re: Why is unique constraint needed for upsert? (treat atomicity as optional) |
| Previous Message | Adrian Klaver | 2014-07-23 20:29:11 | Re: |