| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Wim Bertels <wim(dot)bertels(at)khleuven(dot)be> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: psql latex and newlines |
| Date: | 2012-02-11 00:25:40 |
| Message-ID: | 20120211002540.GA25379@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 12, 2011 at 07:15:12PM +0100, Wim Bertels wrote:
> Hallo,
>
> psql latex output format needs to differentiate between a newline and a
> tabularnewline.
>
> the problem arises when u have a field value that contains a newline
> character, when this field is not the first column, then all the data
> after this newline comes in the first column..
>
> u can try this out, writing a function or table,
> and then add 'enters' or newline in the COMMENT on this function or
> table.
>
> the \pset recordsep doesn't solve this, since the mistakes take place
> within the same record.
Can you give me a self-contained test case I can use so I can use it to
fix the to code?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jasen Betts | 2012-02-11 08:03:56 | Re: " " around fields with psql |
| Previous Message | Chris Travers | 2012-02-10 23:32:36 | Re: Strategy for Primary Key Generation When Populating Table |