| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Wim Bertels <wim(dot)bertels(at)khleuven(dot)be> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Pg General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: psql latex and newlines |
| Date: | 2012-03-15 19:34:43 |
| Message-ID: | 1331840051-sup-9626@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Excerpts from Wim Bertels's message of jue feb 23 12:46:29 -0300 2012:
> > > > > 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 option i came across is the usage of \pbox,
> so the suggestion would be to put every field/cell inside a pbox.
Did you come up with a patch for this?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2012-03-15 19:37:04 | Re: yum repository packages 9.0 and 9.1 libpq conflict |
| Previous Message | Andrus | 2012-03-15 19:33:00 | How to perform full text search |