David G. Johnston wrote:
> > So I guess:
>
> "
> crosstabview with only 2 output columns
> "
>
> https://wiki.postgresql.org/wiki/Crosstabview
> (last section on that page)
>
> never got implemented
It was implemented but eventually removed.
I will update shortly this wiki
David G. Johnston wrote:
> "
> crosstabview with only 2 output columns
> "
>
> https://wiki.postgresql.org/wiki/Crosstabview
> (last section on that page)
>
> never got implemented
It was implemented in Daniel's patch. I removed it before commit and
failed to notice the reference i
On Wed, Apr 13, 2016 at 12:29 PM, Tom Lane wrote:
> Christoph Berg writes:
> > Another thing about \crosstabview:
>
> > # select 1,2 \crosstabview
> > The query must return at least two columns to be shown in crosstab
>
> > s/two/three/, I guess.
>
> Yeah, I noticed that. See
> http://www.postg
Christoph Berg writes:
> Another thing about \crosstabview:
> # select 1,2 \crosstabview
> The query must return at least two columns to be shown in crosstab
> s/two/three/, I guess.
Yeah, I noticed that. See
http://www.postgresql.org/message-id/10276.1460569...@sss.pgh.pa.us
Re: Tom Lane 2016-04-13 <1854.1460562...@sss.pgh.pa.us>
> Hm, we do not have entries attached to any other psql
> meta-commands. Maybe they all should have one, or maybe not, but
> I'm unconvinced about adding one for just this command. What I did
> instead was to make a link target (which there
Christoph Berg writes:
>> Here's a small doc patch that removes the bogus space in "colH [:scolH]"
>> (otherwise psql complains that it is ignoring the 4th parameter.
>> It also adds an index entry and adds a note to the old crosstab
>> functions to make people aware of \crosstabview.
> I should
Re: To PostgreSQL Hackers 2016-04-13 <20160413092312.ga21...@msg.df7cb.de>
> Re: Alvaro Herrera 2016-04-09 <20160408232553.GA721890@alvherre.pgsql>
> > It's useful, no doubt.
>
> It's cool :)
>
> > I pushed it.
>
> Here's a small doc patch that removes the bogus space in "colH [:scolH]"
> (other
