| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Fetter <david(at)fetter(dot)org>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH v5] Show detailed table persistence in \dt+ |
| Date: | 2019-07-02 20:29:10 |
| Message-ID: | 3076E7C5-97B6-4739-9894-0E58712194CC@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 2 Jul 2019, at 22:16, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> even if we made a test case that presumed
> --enable-nls and tried to exercise this, the lack of translations
> for the new words would get in the way for a long while.
For testing though, couldn’t we have an autogenerated .po which has a unique
and predictable dummy value translation for every string (the string backwards
or something), which can be used for testing? This is all hand-wavy since I
haven’t tried actually doing it, but it seems a better option than waiting for
.po files to be available. Or am I missing the point of the value of the
discussed test?
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-07-02 20:35:26 | Re: [PATCH v5] Show detailed table persistence in \dt+ |
| Previous Message | Tom Lane | 2019-07-02 20:16:27 | Re: [PATCH v5] Show detailed table persistence in \dt+ |