Re: xmlserialize bug - extra empty row at the end - Mailing list pgsql-hackers

From Jim Jones
Subject Re: xmlserialize bug - extra empty row at the end
Date
Msg-id 5e3c0501-9e79-cb97-ef96-d27eed417ea6@uni-muenster.de
Whole thread Raw
In response to Re: xmlserialize bug - extra empty row at the end  (Isaac Morland <isaac.morland@gmail.com>)
List pgsql-hackers

My inclination would be, if we're just calling to a long-standardized library routine, to just accept its output as is. If a program is saving the output to a text file, that would be the expected behaviour. If not, then we need to document that the output of our function is the output of the library function, minus the trailing newline.

After some digging on the matter, I'd also tend to leave the output as is, but I also do understand the other arguments - specially the consistency with jsonb_pretty().

If we agree to remove it, the change wouldn't be substantial :) I guess we could just pchomp it in the end of the function, as suggested by Tom. Attached a draft patch.

Best, Jim

Attachment

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: run pgindent on a regular basis / scripted manner
Next
From: Magnus Hagander
Date:
Subject: Re: run pgindent on a regular basis / scripted manner