PostgreSQL jsonb values are truncated in result view and CSV export

[bootun]

Bug Description

When viewing long jsonb values in DBCode, the content is truncated and cannot be viewed completely.

The same truncation happens in multiple places:

• Directly browsing table data
• Viewing the value through a SQL query
• Exporting the result to CSV

For long jsonb fields, DBCode shows only partial content and appends a size marker such as ... (~2KB). Currently I cannot find a way to view or export the full original jsonb value inside DBCode.

The related table/data below has been anonymized.

Repro steps

1. Connect to a PostgreSQL database in DBCode.
2. Create a table with a jsonb column, for example:

CREATE TABLE public.example_generation_record (
    id bigint NOT NULL,
    -- ...
    reference_files jsonb DEFAULT '[]'::jsonb NOT NULL,
    -- ...
);

3. Insert or query a row containing a relatively long jsonb value, for example:

INSERT INTO public.example_generation_record (
    id,
    ...
    reference_files,
    ...
) VALUES (
    1,
    ...
    '[
      {
        "id": "prop:00000000-0000-0000-0000-000000000000",
        "url": "https://example.com/uploaded-files/example-image.png",
        "type": "image",
        "label": "example image label",
        "source": "asset_context",
        "view_id": "00000000-0000-0000-0000-000000000000",
        "asset_id": "00000000-0000-0000-0000-000000000000",
        "state_id": "00000000-0000-0000-0000-000000000000",
        "metadata": {
          "long_text": "This is a long anonymized jsonb field. Repeat this text many times to make the jsonb value larger than a few KB. This should be enough to reproduce the truncation behavior in the DBCode result grid and CSV export."
        }
      },
      ...
    ]'::jsonb,
  ...
);

4. View the table data directly in DBCode.
5. Run a query such as:

SELECT reference_files
FROM public.example_generation_record
WHERE id = 1;

6. Observe that the jsonb value is truncated and ends with something like:

... (~2KB)

7. Export the query result or table data as CSV.
8. Open the exported CSV and observe that the exported value is also truncated.

Expected Behavior

DBCode should provide a way to view and export the full jsonb value.

For example:

• The result grid could show a truncated preview, but allow opening the full cell value in a separate viewer/editor.
• SQL query results should preserve the full value internally.
• CSV export should export the complete original jsonb content, not the truncated display preview.

Actual Behavior

Long jsonb values are truncated in the DBCode UI.

The truncated value appears to include a size marker like:

... (~2KB)

The same truncated content is also exported to CSV, so the original full jsonb data cannot be retrieved through DBCode.

Environment

• DBCode version: 1.31.2
• VS Code (or fork) version: 1.120.0 (Universal)
• OS: MacOS
• Database: PostgreSQL
• Connection: direct

Error Meesages (if applicable)

No error message is shown. The jsonb value is silently truncated.

Screenshots

If applicable, add screenshots showing:

• The truncated jsonb value in the result grid
• The ... (~2KB) suffix
• The exported CSV containing the same truncated value

Logs

If available, paste relevant logs from the Output panel: View > Output > DBCode.

[mikeburgh]

I am having trouble replicating this to track it down.. I tried a few different things and as you can see in the video below, cut paste, click into edit, copy (same code path as export) csv all give me back the full data.. if I expand the row a lot I can see the (~xx) marker but still clicking in and other things don't trigger it..

Screen.Recording.2026-05-20.at.11.46.47.AM.mov

So trying to track down why you are seeing it.. I tried wrap column text and a few other things..

Can you test with this script and see if you can replicate it.. wondering if it's somerthing specific about the number of columns you have or something in the table.

  CREATE TABLE truncation_test (
      id          serial PRIMARY KEY,
      big_json    jsonb,
      big_text    text,
      small_json  jsonb,
      small_text  text
  );

  INSERT INTO truncation_test (big_json, big_text, small_json, small_text) VALUES (
      jsonb_build_object('padding', repeat('x', 800), 'tail', 'END_MARKER_Z'),
      repeat('y', 800) || ' END_MARKER_Z',
      '{"label":"small END_MARKER_Z"}'::jsonb,
      'short value END_MARKER_Z'
  );

select * from truncation_test

[bootun]

In the example you provided, it’s normal. Here are my actual data:

SELECT COUNT(*) FROM public.example_generation_record;
-- 294

-- DDL
CREATE TABLE public.shot_generation_record (
    id bigint NOT NULL,
    fieldA bigint NOT NULL,
    fieldB bigint NOT NULL,
    fieldC bigint NOT NULL,
    fieldD bigint NOT NULL,
    fieldE text DEFAULT ''::text NOT NULL,
    fieldF integer NOT NULL,
    reference_files jsonb DEFAULT '[]'::jsonb NOT NULL,
    fieldG jsonb,
    fieldH character varying,
    fieldI character varying,
    fieldJ bigint,
    fieldK character varying,
    fieldL smallint NOT NULL,
    fieldM text,
    fieldN text,
    created_at timestamp with time zone DEFAULT now() NOT NULL,
    updated_at timestamp with time zone DEFAULT now() NOT NULL,
    CONSTRAINT ck_shot_generation_record_duration_positive CHECK ((duration_seconds > 0))
);

data:

"reference_files"
"[
  {
    ""id"": ""prop:dac531b5-3639-4a69-96a7-ca5a922c1d0f"",
    ""type"": ""image"",
    ""label"": ""蓝钻项链 · 展示状态 · 正面"",
    ""source"": ""asset_context"",
    ""view_id"": ""dac531b5-3639-4a69-96a7-ca5a922c1d0f"",
    ""asset_id"": ""d991f647-583f-45e2-b894-7d6f01dcd591"",
    ""state_id"": ""243583fa-a3ce-4803-b4ab-afac05866573"",
    ""view_kind"": ""front"",
    ""view_name"": ""正面"",
    ""asset_type"": ""prop"",
    ""state_name"": ""展示状态""
  },
  {
    ""id"": ""prop:dce80e61-daa9-465b-87cf-351082cec934"",""type... (~2KB)"

[mikeburgh]

Thanks, one other thought.. should not matter.. but did you open a table or run a query ? and if it was a query are you in a notebook or the editor ?

[bootun]

Oh, I opened it on a table, and the query worked fine!

[mikeburgh]

Thanks, the sample script let me track it down.. fixed in 1.33.0 which has been released.