[BUG]: 1.0.0-beta.2 - `drizzle-kit push` does consider json (jsonb) key order relevant

[michaelschufi]

Report hasn't been filed before.

• I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?

1.0.0-beta.2-0f52822

What version of drizzle-kit are you using?

1.0.0-beta.2-0f52822

Other packages

No response

Describe the Bug

Drizzle Kit is not ignoring the order of json object keys when diffing the default of a Postgres (v17) jsonb column for the command drizzle-kit push.

Repro

1. Define a default value for a jsonb column

   data: jsonb('data')
     .$type<SomeType>()
     .notNull()
     .default({
       b: 2,
       a: 1,
     })

   Notice the key b is defined before a.
2. Run drizzle-kit push
3. Confirm the initial column def. E.g. ALTER TABLE public.myTable ADD "data" jsonb DEFAULT '{"a": 1, "b": 2}'::jsonb NOT NULL;
4. Run drizzle-kit push again

Expected vs. Actual

I expect the push command to complete since no changes are necessary. However, we see that drizzle-kit wants to update the default value of the column again:

┌─── public.myTable.data column changed: 
│ default: '{"bar": {"a": 1, "b": 2}}' -> '{"b":2,"a":1}' 
├─── 
│ ALTER TABLE "myTable" ALTER COLUMN "data " SET DEFAULT '{"b":2,"a":1}'; 
└───

Note
drizzle-kit won't update the column again if the order of the keys b and a are swapped (a first, then b).

Also, a quick shoutout to all of the maintainers for the beta release. Many longstanding bugs in drizzle-kit don't happen anymore and I'm really happy to use it more now.

[tt-a1i]

Found the root cause. The issue is in how JSON defaults are compared:

Serialization path (drizzle-kit/src/serializer/pgSerializer.ts:255):

columnToSet.default = \`'${JSON.stringify(column.default)}'::jsonb\`;

JSON.stringify() preserves the key order from your source code, producing '{"b":2,"a":1}'::jsonb.

Introspection path: When PostgreSQL returns the default value, it normalizes the JSON (keys sorted alphabetically), giving you '{"a": 1, "b": 2}'::jsonb.

Comparison: The differ uses json-diff library on the string representations, so:

• From DB: '{"a": 1, "b": 2}'::jsonb
• From schema: '{"b":2,"a":1}'::jsonb

These don't match as strings, even though they represent the same JSON semantically.

Fix options:

1. Normalize JSON defaults before comparison (parse, sort keys, re-stringify)
2. Use a JSON-aware comparison for json/jsonb column defaults
3. Sort keys during serialization with JSON.stringify(column.default, Object.keys(column.default).sort())

Option 3 would be the least invasive - just change the serialization to use stable key ordering so it matches PostgreSQL's behavior.

[AndriiSherman]

should be fixed in drizzle-kit@1.0.0-beta.6 and drizzle-orm@1.0.0-beta.6