3 people b64e70753a fix(postgres): render internal "char" type as character, not ASCII code (#669) (#811) ...

PostgreSQL's internal "char" type (OID 18, e.g. pg_depend.deptype,
pg_shdepend.deptype) is a single byte the driver decodes as i8. In
pg_value_to_json it had no dedicated branch and fell through to the i8
arm below, surfacing the raw ASCII code (110 for 'n') instead of the
character.

Add a "char" branch that renders the byte as its character (matching
psql's charout): a zero byte becomes an empty string, any other byte is
interpreted as a Latin-1 code point so the output is always valid UTF-8
and never panics. SQL standard CHAR(n)/character(n) is a different type
("bpchar") and is unaffected. Added a unit test.

Co-authored-by: vrustx <vrustx@vrustxdeMac-mini.local>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-07 14:25:04 +08:00

..

assets

feat(iotdb): add Apache IoTDB support

2026-06-07 10:29:05 +08:00

src

fix(postgres): render internal "char" type as character, not ASCII code (#669) (#811)

2026-06-07 14:25:04 +08:00

tests

feat(iotdb): add Apache IoTDB support

2026-06-07 10:29:05 +08:00

Cargo.toml

fix(redis): need to enable tls-rustls-insecure to support --insecure (#794)

2026-06-06 00:15:52 +08:00