Skip to content

fix(postgres): round-trip timestamptz / bytea / jsonb / arrays in the grid #789

Description

@ZhuchkaTriplesix

Summary

Table Browser uses convertResultRowsToStringsAdaptiveinternObjectObject.toString. postgres_table_utils.convertResultRowsToStrings (ISO DateTime) is unused. information_schema.columns.data_type is ARRAY / USER-DEFINED for arrays, enums, domains — formatLiteral then guesses.

Untouched bytea is OK if the column is not in SET. Editing timestamptz / bytea / jsonb / composite / enum cells is not a faithful round-trip.

Scope

  • Display using PG-literal-friendly encoding (ISO timestamps, \\x hex for bytea, JSON text for jsonb). Prefer udt_name (or format_type) over data_type for the codec.
  • Tests against docker/postgres/init/03_all_types.sql (or a subset): timestamptz, bytea, jsonb, enum, int[].

Out of scope

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdata-gridInteractive data grid, cell editor, filtering, groupingsfrontendTheme parser epic label: frontend

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions