2017-11-10 16:38 GMT+01:00 Fabien COELHO :
>
> Hello,
>
> Maybe I'm missing something, but it looks that it could be made to work
>>> without adding another boolean.
>>>
>>
>> The tuples only cannot be disabled, because then other parts print number
>> of rows
>>
>> postgres=# \pset format unalign
Hello,
Maybe I'm missing something, but it looks that it could be made to work
without adding another boolean.
The tuples only cannot be disabled, because then other parts print number
of rows
postgres=# \pset format unaligned
Output format is unaligned.
postgres=# select 10 as a, 20 as b;
2017-11-10 8:12 GMT+01:00 Fabien COELHO :
>
> ISTM that you can remove "force_column_header" and just set "tuple_only"
>>> to what you need, that is you do not need to change anything in function
>>> "print_unaligned_text".
>>>
>>
>> Last point is not possible - I would not to break original tuple
ISTM that you can remove "force_column_header" and just set "tuple_only"
to what you need, that is you do not need to change anything in function
"print_unaligned_text".
Last point is not possible - I would not to break original tuple only mode.
Hmmm... I do not understand. I can see only on
2017-11-09 21:12 GMT+01:00 Pavel Stehule :
>
>
> 2017-11-09 21:03 GMT+01:00 Fabien COELHO :
>
>>
>> Hello Pavel,
>>
>> I hope so I fixed all mentioned issues.
>>>
>>
>> Patch applies with a warning:
>>
>> > git apply ~/psql-graw-2.patch
>> /home/fabien/psql-graw-2.patch:192: new blank line at EO
2017-11-09 21:03 GMT+01:00 Fabien COELHO :
>
> Hello Pavel,
>
> I hope so I fixed all mentioned issues.
>>
>
> Patch applies with a warning:
>
> > git apply ~/psql-graw-2.patch
> /home/fabien/psql-graw-2.patch:192: new blank line at EOF.
> +
> warning: 1 line adds whitespace errors.
>
> Otherw
Hello Pavel,
I hope so I fixed all mentioned issues.
Patch applies with a warning:
> git apply ~/psql-graw-2.patch
/home/fabien/psql-graw-2.patch:192: new blank line at EOF.
+
warning: 1 line adds whitespace errors.
Otherwise it compiles. "make check" ok. doc gen ok.
Two spurious empty
Hi
2017-08-24 5:50 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> I have added the patch to the next commitfest.
>
> Patch applies, compiles, works.
>
> I'm okay with the names graw/graw+, and for having such short-hands.
>
> Missing break in switch, even if last item and useless, because other
>
Argh, sorry, I put it in the September commitfest, and it seems that it
cannot be changed afterwards.
Maybe you can close it and redeclare it in the commitfest you want?
It can be moved
Indeed it can. Feel free to move it, then.
--
Fabien.
--
Sent via pgsql-hackers mailing list (pgsql-ha
2017-08-24 17:27 GMT+02:00 Fabien COELHO :
>
> Hello,
>
> I'll wait to winter commitfest
>>
>
> Argh, sorry, I put it in the September commitfest, and it seems that it
> cannot be changed afterwards.
>
> Maybe you can close it and redeclare it in the commitfest you want?
>
It can be moved
>
> f
Hello,
I'll wait to winter commitfest
Argh, sorry, I put it in the September commitfest, and it seems that it
cannot be changed afterwards.
Maybe you can close it and redeclare it in the commitfest you want?
for some other ideas, tests, comments - it is topic for PostgreSQL 11,
and then
2017-08-24 8:53 GMT+02:00 Fabien COELHO :
>
> "column_header" is somehow redundant with "tuples_only". Use the
>>> existing one instead of adding a new one?
>>>
>>
>> It is different - a result of tuples_only is just tuples - not column
>> names, not title, footer. I needed new special flag for en
"column_header" is somehow redundant with "tuples_only". Use the
existing one instead of adding a new one?
It is different - a result of tuples_only is just tuples - not column
names, not title, footer. I needed new special flag for enhancing
tuples_only to print column names
I do not unders
Hi
2017-08-24 5:50 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> I have added the patch to the next commitfest.
>
> Patch applies, compiles, works.
>
> I'm okay with the names graw/graw+, and for having such short-hands.
>
> Missing break in switch, even if last item and useless, because other
>
Hello Pavel,
I have added the patch to the next commitfest.
Patch applies, compiles, works.
I'm okay with the names graw/graw+, and for having such short-hands.
Missing break in switch, even if last item and useless, because other
items do it... Also should be added at its place in alphabetic
Hi
2017-08-22 11:22 GMT+02:00 Pavel Stehule :
>
>
> 2017-08-22 10:46 GMT+02:00 Fabien COELHO :
>
>>
>> Hello Pavel,
>>
>> One my idea is introduction new simple output format and execution command
>>> with result in this format.
>>>
>>> It should work something like
>>>
>>> \setenv GNUPLOT_OPTION
2017-08-22 10:36 GMT+02:00 Aleksander Alekseev :
> Hi Pavel,
>
> > I am thinking about printing graphs in psql (mainly some histograms). I
> > found so gnuplot is able do very good graphs in console. The one issue is
> > user friendly (with less steps) generating data in good format for this
> > a
2017-08-22 10:46 GMT+02:00 Fabien COELHO :
>
> Hello Pavel,
>
> One my idea is introduction new simple output format and execution command
>> with result in this format.
>>
>> It should work something like
>>
>> \setenv GNUPLOT_OPTION '..'
>> SELECT * FROM data
>> \graw | gnuplot ...
>>
>
> I
Hello Pavel,
One my idea is introduction new simple output format and execution command
with result in this format.
It should work something like
\setenv GNUPLOT_OPTION '..'
SELECT * FROM data
\graw | gnuplot ...
I understand that it is kind of a shortcut for:
\pset fieldsep ' '
\p
Hi Pavel,
> I am thinking about printing graphs in psql (mainly some histograms). I
> found so gnuplot is able do very good graphs in console. The one issue is
> user friendly (with less steps) generating data in good format for this
> application.
>
> One my idea is introduction new simple outpu
20 matches
Mail list logo
