We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drizzle-orm
0.36.3
drizzle-kit
0.28.1
No response
Drizzle Studio row editor doesn't let using strings (a valid JSON object!) in a JSON column. Video demonstration: https://youtu.be/XeFh62uAOag
jsonb
"foo"
{"foo": "bar"}
Same as I expect from INSERT INTO items (id, name) VALUES ('test', '"a json stringy!!"'); - creating a row with JSON column name containing a string.
INSERT INTO items (id, name) VALUES ('test', '"a json stringy!!"');
name
Postgres with pg driver.
pg
import { boolean, jsonb, pgTable, varchar } from "drizzle-orm/pg-core"; type Translatable = { ua: string | null; ru: string | null; en: string | null; } | string; const translatable = () => jsonb().$type<Translatable>(); export const items = pgTable("items", { id: varchar({ length: 128 }).primaryKey(), name: translatable(), description: translatable(), sellable: boolean().default(true), });
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Report hasn't been filed before.
What version of
drizzle-orm
are you using?0.36.3
What version of
drizzle-kit
are you using?0.28.1
Other packages
No response
Describe the Bug
What is the undesired behavior?
Drizzle Studio row editor doesn't let using strings (a valid JSON object!) in a JSON column.
Video demonstration: https://youtu.be/XeFh62uAOag
What are the steps to reproduce it?
jsonb
column in schema"foo"
, not{"foo": "bar"}
)What is the desired result?
Same as I expect from
INSERT INTO items (id, name) VALUES ('test', '"a json stringy!!"');
- creating a row with JSON columnname
containing a string.What database engine are you using?
Postgres with
pg
driver.Schema
The text was updated successfully, but these errors were encountered: