"\u0000" in sql will lead to invalid message format error

INSERT INTO "content"(
    "name"
)
VALUES
    (
        '"1234\u0000"',
    );

OK with command line. not OK with ng.

[vitaly-t]

@brianc , @charmander

Guys, I’m afraid this issue was closed prematurely. There is indeed a bug in the driver related specifically to Unicode symbol \u0000, which results in throwing error invalid message format.

This one works fine:

select E'\u0001' as value

And these ones throw that error:

select E'\u0000' as value

select '\0' as value

This needs to be re-opened, and escalated into a bug.

[sehrope]

The error message difference is due to the lack of escaping the backslash in the JS code so the \u0000 is evaluated in the client, not by the server. This makes the query string itself sent to the backend contain an invalid 0-byte and thus gets rejected differently.

Here’s the two situations:

// Single backslash evaluated to a zero byte locally which is rejected at message level by server:
> client.query("SELECT E'\u0000'").catch((err) => console.error('%s', err)).then(console.log)
error: invalid message format

// Double backslash gets sent to the server correctly
> client.query("SELECT E'\\u0000'").catch((err) => console.error('%s', err)).then(console.log)
error: invalid Unicode escape value at or near "E'\u0000"

You can see it in the lengths of the strings too:

// Single backslash
> console.log('%s', "SELECT E'\u0000'".length);
11
// Double backslash
> console.log('%s', "SELECT E'\\u0000'".length);
16

This does indicate a bug but not directly related to these error messages. The driver shouldn’t be sending strings with zero bytes to the backend as that’s invalid and a potential security issue. I’m going to open a separate issue for rejecting those queries in the client as they violate the FEBE protocol.