| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | bruce(at)momjian(dot)us |
| Cc: | zmlpostgres(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org, rjuju123(at)gmail(dot)com |
| Subject: | Re: COPY TO (FREEZE)? |
| Date: | 2023-10-30 06:16:58 |
| Message-ID: | 20231030.151658.744161460517379332.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Sun, 29 Oct 2023 15:35:02 -0400, Bruce Momjian <bruce(at)momjian(dot)us> wrote in
> You are 100% correct. Updated patch attached.
- errmsg("COPY force not null only available using COPY FROM")));
+ errmsg("COPY force not null cannot be used with COPY TO")));
I find the term "force not null" hard to translate, especially into
Japaese, as its literal translation doesn't align with the entire
message. The most recent translation for it is the literal rendition
of "FORCE_NOT_NULL option of COPY can only be used with COPY FROM".
In short, for translation convenience, I would prefer if "force not
null" were "FORCE_NOT_NULL".
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2023-10-30 06:20:40 | Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock |
| Previous Message | Ashutosh Bapat | 2023-10-30 04:46:00 | Re: BRIN minmax multi - incorrect distance for infinite timestamp/date |