0.55.2

Merged PRs

doltgresql

• 2323: Fixed issues 2316 and 2318
  This fixes:
  • #2316
  • #2318
    For 2316, clients may only send a single format code that should apply to multiple values, but we assumed that their lengths always matched. This is fixed by extending the format code slice length to the same as the value slice if there is a single format code provided.
    For 2318, it appears that Rust wants these values in binary format, so now we're returning them in binary format. I'm not sure why Rust doesn't accept text format like everything else does, but perhaps it's the default in Postgres so some ORMs only work with the default.
    It's worth mentioning that tests for these exist only within the client tests, as I could not replicate the errors within our standard testing framework. As mentioned with the binary format, it seems that Rust isn't as permissive as other ORMs, so we have to test with Rust specifically.

Closed Issues

• 2318: Extended protocol sends TIMESTAMPTZ and DATE as text instead of binary format
• 2316: Extended protocol INSERT/UPDATE/DELETE crashes with 'index out of range [1] with length 1'