Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used
| От | Tom Lane |
|---|---|
| Тема | Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used |
| Дата | |
| Msg-id | 25846.1359407305@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used (Dean Rasheed <dean.a.rasheed@gmail.com>) |
| Ответы |
Re: Re: proposal: a width specification for s specifier
(format function), fix behave when positional and ordered placeholders are used
|
| Список | pgsql-hackers |
Dean Rasheed <dean.a.rasheed@gmail.com> writes:
> On 28 January 2013 20:40, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> 2013/1/28 Dean Rasheed <dean.a.rasheed@gmail.com>:
>>> flags - not currently implemented. Pavel's second patch adds support
>>> for the '-' flag for left justified string output. However, I think
>>> this should support all datatypes (i.e., %I and %L as well as %s).
>> no - surely not - I% and L% is PostgreSQL extension and left or right
>> alignment is has no sense for PostgreSQL identifiers and PostgreSQL
>> literals.
> Left/right alignment and padding in printf() apply to all types, after
> the data value is converted to a string. Why shouldn't that same
> principle apply to %I and %L?
I agree with Dean --- it would be very strange for these features not to
apply to all conversion specifiers (excepting %% of course, which isn't
really a conversion specifier but an escaping hack).
regards, tom lane
В списке pgsql-hackers по дате отправления: