From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [Fwd: Make psql use all pretty print options] |
Date: | 2003-10-14 15:17:44 |
Message-ID: | 9448.1066144664@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> Resubmission of patch (for 7.4).
While I agree with the objection that we shouldn't break the strings
freeze for this, I do think it might be a good idea to apply the change
that prints CHECK constraints using pg_get_constraintdef() rather than
simply looking at pg_constraint.consrc. This is arguably a bug fix,
not a pretty printing improvement, because consrc doesn't track column
renamings (and probably other changes).
Doing that would require making this one string change:
! printfPQExpBuffer(&buf, _(" \"%s\" CHECK %s"),
becomes
! printfPQExpBuffer(&buf, _(" \"%s\" %s"),
but ISTM the latter string doesn't really need any translation and so
it wouldn't be much of a problem.
Comments?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-10-14 16:04:15 | Re: fix for strict-alias warnings |
Previous Message | Andrew Dunstan | 2003-10-14 14:56:09 | Re: fix for strict-alias warnings |