From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Jan Michálek <godzilalalala(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Other formats in pset like markdown, rst, mediawiki |
Date: | 2017-03-09 19:10:54 |
Message-ID: | f9378ba5-782e-ec67-cfcc-d6fa87d5c941@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 (\t) mode. (rst and markdown)
- rst: Do something about \pset title; the way it currently shows up
appears to be invalid; could use ".. table:: title" directive
- markdown: Extra blank line between table and footer.
- markdown: We should document or comment somewhere exactly which of the
various markdown table formats this is supposed to produce. (Pandoc
pipe_tables?)
- markdown: Table title needs to be after the table, like
Table: title
- markdown: Needs to escape | characters in cell contents. (Not
needed for rst.) More escaping might be needed.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-03-09 19:14:30 | Re: bytea_output vs make installcheck |
Previous Message | Sven R. Kunze | 2017-03-09 19:04:45 | Re: SQL/JSON in PostgreSQL |