Replies: 1 comment
-
I don't think this can be changed at this point in a backwards compatible manner. I think you will need to wrap or rename the type to override the JSON logic. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm developing a web pg client using pgproto3, but I found that when I using DataRow.MarshalJSON to parse the DataRow message, it will turn string which contains LF or VT into HEX string.
pgx/pgproto3/data_row.go
Lines 97 to 100 in 6f2ce92
Because the ASCII of LF is 9 , and the ASCII of VT is 11.
But LF AND VT are often used in some text column.
Could we have some special treatment for these frequently-used ASCII ?
Beta Was this translation helpful? Give feedback.
All reactions