Re: xmlserialize bug - extra empty row at the end

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: xmlserialize bug - extra empty row at the end
Дата
Msg-id CAFj8pRBvfM=a4SYHyv7bTCYmXt=Fo5GcsNuOtctQO5CApRrYHA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: xmlserialize bug - extra empty row at the end  (Isaac Morland <isaac.morland@gmail.com>)
Ответы Re: xmlserialize bug - extra empty row at the end  (Isaac Morland <isaac.morland@gmail.com>)
Список pgsql-hackers


Dne ne 23. 4. 2023 18:03 uživatel Isaac Morland <isaac.morland@gmail.com> napsal:
On Sun, 23 Apr 2023 at 10:52, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Isaac Morland <isaac.morland@gmail.com> writes:
 
> I might go so
> far as to change the psql display routines to not leave a blank line after
> the content in the event it ends with a newline.

psql has *no* business changing what it displays: if what came from the
server has a trailing newline, that had better be made visible.  Even if
we thought it was a good idea, it's about 25 years too late to reconsider
that.  However, xmlserialize()'s new indenting behavior isn't set in
stone yet, so we could contemplate chomping newlines within that.

The trailing newline is made visible by the little bent arrow character that appears at the right hand side. So you could still tell whether the value ended with a trailing newline. I agree that simply dropping the trailing newline before displaying the value would be a very bad idea.

What is benefit or usage of this trailing newline?

Personally, when I do some formatting I prefer adding newlines on client side before necessity of removing.



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Isaac Morland
Дата:
Сообщение: Re: xmlserialize bug - extra empty row at the end
Следующее
От: Isaac Morland
Дата:
Сообщение: Re: xmlserialize bug - extra empty row at the end