Thanks
2017-09-18 15:33 GMT+02:00 Daniel Gustafsson :
> > On 18 Sep 2017, at 15:31, Jan Michálek wrote:
> >
> > I have`t any new version recently, because i was waiting for new
> version. But I will have some time on this in next months. How many time I
> have to next freeze?
>
> The next commit
> On 18 Sep 2017, at 15:31, Jan Michálek wrote:
>
> I have`t any new version recently, because i was waiting for new version. But
> I will have some time on this in next months. How many time I have to next
> freeze?
The next commitfest runs from 2017-11-01 to 2017-11-30, I will move your patc
I have`t any new version recently, because i was waiting for new version.
But I will have some time on this in next months. How many time I have to
next freeze?
Thanks Je;
2017-09-13 1:14 GMT+02:00 Daniel Gustafsson :
> > On 08 May 2017, at 12:02, Fabien COELHO paristech.fr> wrote:
> >
> > Hell
> On 08 May 2017, at 12:02, Fabien COELHO
> wrote:
>
> Hello Jan,
>
> Please give a number to submitted patches. I think that this was v3.
>
> The patch does NOT fix various issues I pointed out in my previous review:
>
> - tabs introduced in "doc/src/sgml/ref/psql-ref.sgml"
> - too long help
Hello Jan,
Please give a number to submitted patches. I think that this was v3.
The patch does NOT fix various issues I pointed out in my previous review:
- tabs introduced in "doc/src/sgml/ref/psql-ref.sgml"
- too long help line in "src/bin/psql/help.c"
- spurious space after a comma in "s
Hello Jan,
Please give a number to submitted patches. I think that this was v3.
The patch does NOT fix various issues I pointed out in my previous review:
- tabs introduced in "doc/src/sgml/ref/psql-ref.sgml"
- too long help line in "src/bin/psql/help.c"
- spurious space after a comma in
2017-04-19 10:05 GMT+02:00 Jan Michálek :
> 2017-04-19 9:18 GMT+02:00 Fabien COELHO :
>
>>
>> I still do not understand "why" this variant vs CommonMark or whatever
other version.
>>>
>>> Because of simply implementation and readability (looks similar to
>>> aligned
>>> format) and it is
2017-04-19 9:18 GMT+02:00 Fabien COELHO :
>
> I still do not understand "why" this variant vs CommonMark or whatever
>>> other version.
>>>
>>
>> Because of simply implementation and readability (looks similar to aligned
>> format) and it is comfortable to edit generated table (changing values,
>>
I still do not understand "why" this variant vs CommonMark or whatever
other version.
Because of simply implementation and readability (looks similar to aligned
format) and it is comfortable to edit generated table (changing values,
aligning columns etc.).
Hmmm. Why not.
Sorry, maybe I`m n
2017-04-18 23:06 GMT+02:00 Fabien COELHO :
>
> Hello,
>
> There are different flavour of markdown, maybe you should document which
>>> one is targetted. Should it be CommonMark? Another variant? Why?
>>>
>>
>> This should be pandoc pipe table. It's because it is similar to aligned
>> format. I nee
Hello,
There are different flavour of markdown, maybe you should document which
one is targetted. Should it be CommonMark? Another variant? Why?
This should be pandoc pipe table. It's because it is similar to aligned
format. I need add this to documentation (i have it in recent TODO)
I stil
2017-04-18 12:06 GMT+02:00 Fabien COELHO :
>
> Hello Jan,
>
> It seems that the patch does not apply anymore on head due to changes in
>>> psql non regression tests. Could you rebase?
>>>
>>
>> This should work on current master (all test passed).
>>
>
> Patch applies, compiles and make check is o
Hello Jan,
It seems that the patch does not apply anymore on head due to changes in
psql non regression tests. Could you rebase?
This should work on current master (all test passed).
Patch applies, compiles and make check is ok.
There are different flavour of markdown, maybe you should doc
2017-04-18 2:27 GMT+02:00 Fabien COELHO :
>
> Hello Jan,
>
> Corrected problem with \pset linestyle when format is set to markdown, or
>> rst.
>>
>> Corrected tuples only for markdown and rst (normal and expanded)
>>
>
> It seems that the patch does not apply anymore on head due to changes in
> ps
2017-04-18 2:27 GMT+02:00 Fabien COELHO :
>
> Hello Jan,
>
> Corrected problem with \pset linestyle when format is set to markdown, or
>> rst.
>>
>> Corrected tuples only for markdown and rst (normal and expanded)
>>
>
> It seems that the patch does not apply anymore on head due to changes in
> ps
Hello Jan,
Corrected problem with \pset linestyle when format is set to markdown, or
rst.
Corrected tuples only for markdown and rst (normal and expanded)
It seems that the patch does not apply anymore on head due to changes in
psql non regression tests. Could you rebase?
--
Fabien.
--
On April 5, 2017 11:19:04 PM PDT, "Jan Michálek"
wrote:
>2017-04-06 0:55 GMT+02:00 Andres Freund :
>
>> Hi,
>>
>> On 2017-04-02 22:28:40 +0200, Jan Michálek wrote:
>> > 2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
>> > > The new status of this patch is: Waiting on Author
>> > >
>> >
>> > Corre
2017-04-06 0:55 GMT+02:00 Andres Freund :
> Hi,
>
> On 2017-04-02 22:28:40 +0200, Jan Michálek wrote:
> > 2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
> > > The new status of this patch is: Waiting on Author
> > >
> >
> > Corrected problem with \pset linestyle when format is set to markdown, or
>
Hi,
On 2017-04-02 22:28:40 +0200, Jan Michálek wrote:
> 2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
> > The new status of this patch is: Waiting on Author
> >
>
> Corrected problem with \pset linestyle when format is set to markdown, or
> rst.
>
> Corrected tuples only for markdown and rst (no
2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
> The following review has been posted through the commitfest application:
> make installcheck-world: tested, passed
> Implements feature: tested, passed
> Spec compliant: tested, passed
> Documentation:tested, passed
>
> H
On Friday, March 31, 2017 7:17:08 AM CEST, Jan Michálek wrote:
2017-03-30 21:53 GMT+02:00 Pavel Stehule :
2017-03-29 20:11 GMT+02:00 Jan Michálek :
2017-03-27 19:41 GMT+02:00 Jan Michálek :
2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
The following review has been posted through the comm
2017-03-31 12:01 GMT+02:00 Pierre Ducroquet :
> On Friday, March 31, 2017 7:17:08 AM CEST, Jan Michálek wrote:
>
>>
>>
>> 2017-03-30 21:53 GMT+02:00 Pavel Stehule :
>>
>>
>> 2017-03-29 20:11 GMT+02:00 Jan Michálek :
>>
>>
>> 2017-03-27 19:41 GMT+02:00 Jan Michálek :
>>
>>
>> 2017-03-23 17:26 GMT+0
2017-03-30 21:53 GMT+02:00 Pavel Stehule :
>
>
> 2017-03-29 20:11 GMT+02:00 Jan Michálek :
>
>>
>>
>> 2017-03-27 19:41 GMT+02:00 Jan Michálek :
>>
>>>
>>>
>>> 2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
>>>
The following review has been posted through the commitfest application:
make i
2017-03-29 20:11 GMT+02:00 Jan Michálek :
>
>
> 2017-03-27 19:41 GMT+02:00 Jan Michálek :
>
>>
>>
>> 2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
>>
>>> The following review has been posted through the commitfest application:
>>> make installcheck-world: tested, passed
>>> Implements feature:
2017-03-27 19:41 GMT+02:00 Jan Michálek :
>
>
> 2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
>
>> The following review has been posted through the commitfest application:
>> make installcheck-world: tested, passed
>> Implements feature: tested, passed
>> Spec compliant: tested, p
2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
> The following review has been posted through the commitfest application:
> make installcheck-world: tested, passed
> Implements feature: tested, passed
> Spec compliant: tested, passed
> Documentation:tested, passed
>
> H
2017-03-23 17:26 GMT+01:00 Pierre Ducroquet :
> The following review has been posted through the commitfest application:
> make installcheck-world: tested, passed
> Implements feature: tested, passed
> Spec compliant: tested, passed
> Documentation:tested, passed
>
> H
The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, passed
Spec compliant: tested, passed
Documentation:tested, passed
Hi
This is my first review (Magnus said in his presentation
>>I like the idea taking advantage of linestyle utilities
>>to implement rst and markdown format efficiently instead of newly developing
>>pset format things.
>>But I'm thinking two comments below needs change to something about not
>>focusing only linestyle.
>>That's because they really take
e above
>>> documentation (link)
>>>
>>
>> I will look on the comments, this is only work version, coding style
>> issues will be corrected (i have some comments only my orientation in code).
>>
>>
>>>
>>>
>>> - And I also fo
; issues will be corrected (i have some comments only my orientation in code).
>
>
>>
>>
>> - And I also found patch cannot be applied to current master.
>>
>
> I have 9.6.2 source code. It is not correct? Where i find source code i
> should u
master.
>
I have 9.6.2 source code. It is not correct? Where i find source code i
should use?
Have nice day
Jan
>
>
> Regards,
>
> Ideriha, Takeshi
>
>
>
> *From:* pgsql-hackers-ow...@postgresql.org [mailto:pgsql-hackers-owner@
> postgresql.org] *On Behal
resql.org [mailto:pgsql-hackers-owner@
> postgresql.org] *On Behalf Of *Jan Michalek
> *Sent:* Sunday, March 19, 2017 5:10 AM
> *To:* Peter Eisentraut
> *Cc:* Pavel Stehule ; PostgreSQL mailing lists <
> pgsql-hackers@postgresql.org>
> *Subject:* Re: [HACKERS] Other formats
lists
Subject: Re: [HACKERS] Other formats in pset like markdown, rst, mediawiki
2017-03-12 19:21 GMT+01:00 Jan Michálek
mailto:godzilalal...@gmail.com>>:
2017-03-10 9:43 GMT+01:00 Jan Michálek
mailto:godzilalal...@gmail.com>>:
2017-03-09 20:10 GMT+01:00 Peter Eisentraut
mailto:
2017-03-12 19:21 GMT+01:00 Jan Michálek :
>
>
> 2017-03-10 9:43 GMT+01:00 Jan Michálek :
>
>>
>>
>> 2017-03-09 20:10 GMT+01:00 Peter Eisentraut <
>> peter.eisentr...@2ndquadrant.com>:
>>
>>> This is looking pretty neat. I played around with it a bit. There are
>>> a couple of edge cases that you
2017-03-10 9:43 GMT+01:00 Jan Michálek :
>
>
> 2017-03-09 20:10 GMT+01:00 Peter Eisentraut com>:
>
>> This is looking pretty neat. I played around with it a bit. There are
>> a couple of edge cases that you need to address, I think.
>>
>
> Thanks, original code is very synoptical and and well p
I find, there is problem in tab indent in rst, it looks that lines should
be aligned to left in some cases.
2017-03-10 9:43 GMT+01:00 Jan Michálek :
>
>
> 2017-03-09 20:10 GMT+01:00 Peter Eisentraut com>:
>
>> This is looking pretty neat. I played around with it a bit. There are
>> a couple of
2017-03-09 20:10 GMT+01:00 Peter Eisentraut <
peter.eisentr...@2ndquadrant.com>:
> This is looking pretty neat. I played around with it a bit. There are
> a couple of edge cases that you need to address, I think.
>
Thanks, original code is very synoptical and and well prepared for adding
new fo
This is looking pretty neat. I played around with it a bit. There are
a couple of edge cases that you need to address, I think.
- Does not support \x
- When \pset format is rst, then \pset linestyle also shows up as
"rst". That is wrong. Same for markdown.
- Broken output in tuples_only (\
2017-03-06 19:45 GMT+01:00 Peter Eisentraut :
> On 3/5/17 05:40, Jan Michálek wrote:
> > jelen=# \pset linestyle rst
> > Line style is rst.
> > jelen=# \pset format wrapped
> > Output format is wrapped.
> > jelen=# SELECT repeat('Goodnight Irene ', 30);
> > +---
On 3/5/17 05:40, Jan Michálek wrote:
> jelen=# \pset linestyle rst
> Line style is rst.
> jelen=# \pset format wrapped
> Output format is wrapped.
> jelen=# SELECT repeat('Goodnight Irene ', 30);
> +-+
> |
2017-03-06 16:25 GMT+01:00 Pavel Stehule :
>
>
> 2017-03-06 16:17 GMT+01:00 Jan Michálek :
>
>>
>>
>> 2017-03-06 15:19 GMT+01:00 Pavel Stehule :
>>
>>>
>>>
>>> 2017-03-06 0:26 GMT+01:00 Jan Michálek :
>>>
2017-03-05 14:02 GMT+01:00 Jan Michálek :
>
>
> 2017-03-05 13
2017-03-05 14:02 GMT+01:00 Jan Michálek :
>
>
> 2017-03-05 13:39 GMT+01:00 Pavel Stehule :
>
>>
>>
>> 2017-03-05 13:22 GMT+01:00 Pavel Stehule :
>>
>>>
>>>
>>> 2017-03-05 13:08 GMT+01:00 Jan Michálek :
>>>
It is question if it is really new format, because formating is the
same as aligne
2017-03-05 13:39 GMT+01:00 Pavel Stehule :
>
>
> 2017-03-05 13:22 GMT+01:00 Pavel Stehule :
>
>>
>>
>> 2017-03-05 13:08 GMT+01:00 Jan Michálek :
>>
>>> It is question if it is really new format, because formating is the same
>>> as aligned/wrapped format, changed is only style of lines.
>>>
>>
>>
2017-03-05 13:22 GMT+01:00 Pavel Stehule :
>
>
> 2017-03-05 13:08 GMT+01:00 Jan Michálek :
>
>> It is question if it is really new format, because formating is the same
>> as aligned/wrapped format, changed is only style of lines.
>>
>
> Please, don't do top posting https://en.wikipedia.org/wiki/
2017-03-05 13:08 GMT+01:00 Jan Michálek :
> It is question if it is really new format, because formating is the same
> as aligned/wrapped format, changed is only style of lines.
>
Please, don't do top posting
https://en.wikipedia.org/wiki/Posting_style#Top-posting
> 2017-03-05 12:36 GMT+01:00 P
It is question if it is really new format, because formating is the same as
aligned/wrapped format, changed is only style of lines.
2017-03-05 12:36 GMT+01:00 Pavel Stehule :
>
>
> 2017-03-05 11:40 GMT+01:00 Jan Michálek :
>
>> I know, but, both new linestyles are created literally by cloning asc
2017-03-05 11:40 GMT+01:00 Jan Michálek :
> I know, but, both new linestyles are created literally by cloning ascii
> linestyle and few lines in print_aligned_text. Both works with "aligned"
> and "wrapped" format. In rst is wrapped format useful, in my opinion, in
> markdown i can`t find how I ca
I know, but, both new linestyles are created literally by cloning ascii
linestyle and few lines in print_aligned_text. Both works with "aligned"
and "wrapped" format. In rst is wrapped format useful, in my opinion, in
markdown i can`t find how I can get newline in record (maybe it is not
posiible i
If you want to implement a new table format, you should be looking at
\pset format, not \pset linestyle. \pset format sets different table
formats, such as html, latex, and asciidoc. \pset linestyle just
chooses between different styles for the plain-text table format.
On 3/1/17 06:31, Jan Michá
Regression test corrected.
2017-03-01 11:43 GMT+01:00 Jan Michálek :
> Sorry, I have some errors in my diff, i had copy something from bad
> folder. I will fix it.
>
> 2017-03-01 0:27 GMT+01:00 Jan Michálek :
>
>> There it is, what i have.
>> I need i small help with psql.out, because \pset forma
Sorry, I have some errors in my diff, i had copy something from bad folder.
I will fix it.
2017-03-01 0:27 GMT+01:00 Jan Michálek :
> There it is, what i have.
> I need i small help with psql.out, because \pset format wrapped. I don`t
> know, how to have it in fixed width.
>
> 2017-02-28 14:23 GM
There it is, what i have.
I need i small help with psql.out, because \pset format wrapped. I don`t
know, how to have it in fixed width.
2017-02-28 14:23 GMT+01:00 Jan Michálek :
> Current state is something like this (diff is attached).
> I currently haven`t regression test, tab completion etc.,
Current state is something like this (diff is attached).
I currently haven`t regression test, tab completion etc., I will add this
thing following structure of asciidoc commit.
Output is tested using retext, rst is OK, md have problem with cells with
newline (i must find out, how it is possible cr
On Fri, Feb 24, 2017 at 3:09 AM, Jan Michálek wrote:
> I can try it, doesn`t look dificult, but I`m worry, that I`m not able to
> write clean, pretty code.
If you want to have something available in Postgres 10, you had better
be quick. The last commit fest of the development cycle of Postgres 10
2017-02-23 19:09 GMT+01:00 Jan Michálek :
> I can try it, doesn`t look dificult, but I`m worry, that I`m not able to
> write clean, pretty code.
>
It is not a problem, there is lot of iteration for code cleaning
Regards
Pavel
>
> 2017-02-23 18:03 GMT+01:00 Alvaro Herrera :
>
>> Leknín Řepánek
I can try it, doesn`t look dificult, but I`m worry, that I`m not able to
write clean, pretty code.
2017-02-23 18:03 GMT+01:00 Alvaro Herrera :
> Leknín Řepánek wrote:
> > I was mainly using tables in rst, i think, that this format is very
> > similar to "grid tables" in markdown. And it is really
Leknín Řepánek wrote:
> I was mainly using tables in rst, i think, that this format is very
> similar to "grid tables" in markdown. And it is really similar to default
> borders used
> in psql with border 2.
Great. So are you writing the code now? :-)
--
Álvaro Herrerahttps://
I was mainly using tables in rst, i think, that this format is very
similar to "grid tables" in markdown. And it is really similar to default
borders used
in psql with border 2.
On Thu, Feb 23, 2017 at 12:06:36PM -0300, Alvaro Herrera wrote:
> Jan Michálek wrote:
>
> > Is there posibility, that
Jan Michálek wrote:
> Is there posibility, that support for some others formats will be added in
> the future? Or id posible to create some of this formats by manipulating
> with pset? Or I need use xml for export and use some xslt templates, or
> lxml etc. to create format that I will be able to
On Thu, Feb 23, 2017 at 7:29 PM, Jan Michálek wrote:
> Is there possibility, that support for some others formats will be added in
> the future? Or is it possible to create some of this formats by manipulating
> with pset?
Addition of new formats is definitely possible, the latest one added
was a
Have a nice day
I`m using \pset format html for generating tables for some documentation,
training, reports, blogs... Mainly sample of data for SQL queries, or
explaining structure etc.
But in some software like sphinx, wiki on redmine, or markdown on github
issues I`m not able to insert table in h
62 matches
Mail list logo
