On Thu, Jan 23, 2020 at 03:20:27PM -0300, Alvaro Herrera wrote: > On 2020-Jan-23, Bruce Momjian wrote: > > > On Thu, Jan 23, 2020 at 01:05:50PM -0500, Robert Haas wrote: > > > > Another > > > > problem, though, is how do you _flag_ file names as being > > > > base64-encoded? Use another JSON field to specify that? > > > > > > Alvaro's proposed solution in the message to which you replied was to > > > call the field either 'path' or 'path_base64' depending on whether > > > base-64 escaping was used. That seems better to me than having a field > > > called 'path' and a separate field called 'is_path_base64' or > > > whatever. > > > > Hmm, so the JSON key name is the flag --- interesting. > > Yes, because if you use the same key name, you risk a dumb tool writing > the file name as the encoded name. That's worse because it's harder to > figure out that it's wrong.
Yes, good point. I think my one concern is that someone might specify both keys in the JSON, which would be very odd. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
