The generated `type Json = ColumnType<JsonValue, string, string>` should just be `JsonValue` for Postgres.

[afg419]

If I'm not mistaken, the generated json type type Json = ColumnType<JsonValue, string, string> seems to be overly restrictive for Postgres, as I can use kysely to insert and update JsonValue values, in addition to strings. Since JsonValue | string is just JsonValue, the whole thing can be collapsed type Json = JsonValue.

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• We receive the funding once the issue is completed & confirmed by you.
• Thank you in advance for helping prioritize & fund our backlog.

[afg419]

That is, both of these work:

await kysely.insertInto('myTable').values({ address: { street: '111 First Ave', zip: '00000', state: 'MA' }}).executeTakeFirst()

await kysely.insertInto('myTable').values({ address: JSON.stringify({ street: '111 First Ave', zip: '00000', state: 'MA' })}).executeTakeFirst()

[BoscoDomingo]

I came here to post this exact issue. I changed the generated types and it works flawlessly (at least for insertion).

In fact, it works better than inserting a string because (at least in JS/TS) stringifying an object escapes the double quotes, therefore taking up significantly more space than needed. I wouldn't be surprised if that also causes us to lose the SQL optimizations and indexing abilities.

In essence, I echo the OP

[BoscoDomingo]

Pushed a PR, I'm expecting that to work. @RobinBlomberg would love a 👍🏼!