Re: Bug: psql misquotes constraints - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Bug: psql misquotes constraints
Date
Msg-id 1089596202.58812.16.camel@jester
Whole thread Raw
In response to Re: Bug: psql misquotes constraints  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: Bug: psql misquotes constraints  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
I remember a thread about pretty-print functions. Are those used? This
is probably the best place to put the fix, since they already munge
things for display purposes.

On Sun, 2004-07-11 at 21:33, Christopher Kings-Lynne wrote:
> It should be done, otherwise you cannot copy and paste foreign key 
> creation code from the psql output :)
> 
> Chris
> 
> Bruce Momjian wrote:
> 
> > I can do that for 7.6.  Is it worth it?  Is it a TODO?
> > 
> > 
> > ---------------------------------------------------------------------------
> > 
> > Christopher Kings-Lynne wrote:
> > 
> >>>As a result of the constraint output functions being shared between
> >>>pg_dump and psql, some of the output is mis-quoted in the display area
> >>>for columns including quotes. Notice it's correct in the table Column
> >>>list, but the constraint has the escaped versions.
> >>
> >>It's misquoted because psql DOES NOT share the fmtId function with 
> >>pg_dump.  It simply puts double quotes around it.  If you can fix psql 
> >>so that it is able to link to the fmtId function, then you can easily 
> >>fix the problem.
> >>
> >>Chris
> >>
> >>
> >>---------------------------(end of broadcast)---------------------------
> >>TIP 8: explain analyze is your friend
> >>
> > 
> > 



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Bug: psql misquotes constraints
Next
From: Christopher Kings-Lynne
Date:
Subject: Is the time zone comment in postgresql.conf still valid?