Search Postgresql Archives

Re: psql latex and newlines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 10, 2012 at 03:18:27PM +0200, Wim Bertels wrote:
> On vr, 2012-03-30 at 16:25 +0200, Wim Bertels wrote:
> > On do, 2012-03-15 at 16:34 -0300, Alvaro Herrera wrote:
> > > 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?
> 
> A more polished version on page 7 and 8 of the pdf,
> in attachment:
> 1. include the psql latex a separate file
> 2. use longtable instead of table
> 3. if horizontal lines are needed they can easily be uncommented

Looks good.  Can I see the psql patch for this improvement?


-- 
  Bruce Momjian  <bruce@xxxxxxxxxx>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux