Re: Crosstab function

From: "Hengky Liwandouw" <hengkyliwandouw(at)gmail(dot)com>
To: "'Sim Zacks'" <sim(at)compulab(dot)co(dot)il>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Crosstab function
Date: 2014-05-09 02:44:28
Message-ID: 004201cf6b30$9c48c250$d4da46f0$@com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks Sim, a very usefull information.

From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Sim Zacks
Sent: Wednesday, May 07, 2014 7:33 PM
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Crosstab function

What I have done in the past to build a generic reporting application is to
have the function write the results you want in a table and return the
tablename and then have the client code call select * from that table.

My standard report tablename is tblreport || userid;
It gets dropped at the beginning of the function, so it is basically a temp
table that doesn't interfere with any other users.

Example:
execute 'drop table if exists reports.tblreport' || v_userid ;
execute 'drop sequence if exists reports.tblreport' || v_userid ||
'_id_seq; create sequence reports.tblreport' || v_userid || '_id_seq';
v_sql=' create table reports.tblreport' || v_userid || ' as ';

Sim

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Krystian Bigaj 2014-05-09 04:58:19 Re: SSL Compression - doesn't work?
Previous Message Michael Paquier 2014-05-09 00:43:25 Re: How to fix lost synchronization with server