error on jsonb field with binary_parameters

[rothskeller]

I have binary_parameters=yes in my connection string so that I can efficiently set the values of some multimegabyte bytea columns.

Elsewhere in my database, I have jsonb columns. These work fine when binary_parameters is not set, but when it is set, I get "pq: unsupported jsonb version number 123" when updating a record containing a jsonb column.

It seems like I need binary_parameters off when working with jsonb, and on when working with huge bytea. And it's connection string parameter, so I can't have it both ways. Help?

[cbandy]

The binary format for jsonb is prefixed with an 8-bit version. The current version is 1 followed by the plain/text JSON. (See jsonb_recv)

You could cast your []byte or json.RawMessage to string, signaling that it should be identified as text format. Or you could wrap/cast these to a sql.Scanner driver.Valuer that adds the version prefix. (I suspect both incur a copy of the memory...)

Since everything passes through database/sql before arriving at lib/pq, options are limited.

[cbandy]

@rothskeller did you find a solution?

[rothskeller]

Your suggestion of casting to string solved my problem, thanks. My apologies if you were waiting on a response from me.

[ivanovaleksey]

I guess this one could be close :)