You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CREATE TABLE "customers" (
"id" uuid DEFAULT gen_random_uuid(),
"name" text NOT NULL,
"email" text NOT NULL UNIQUE,
"phone_number" text,
"address_line_1" text,
"address_line_2" text,
"address_post_code" text,
"address_state" text,
"address_country" text,
"dob_year" smallint CHECK (dob_year > 1900 AND dob_year <= 9999),
"dob_month" smallint CHECK (dob_month > 0 AND dob_month <= 12),
"notes" text NOT NULL DEFAULT '',
"has_sms_allowed" boolean NOT NULL DEFAULT false,
"has_email_allowed" boolean NOT NULL DEFAULT false,
"created_on" TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT CURRENT_TIMESTAMP,
"updated_on" TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (id)
);
See error
[2022-12-15T08:57:39Z WARN synth::datasource::relational_datasource] Trying to put an unsigned u32 into a int2 typed column customers.dob_month
Error: At namespace "fixtures"
Caused by:
0: Failed to insert data for collection customers
1: One or more database inserts failed: error returned from database: incorrect binary data format in bind parameter 7: incorrect binary data format in bind parameter 7
Expected behavior
It should just insert the numbers.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS: [e.g. Linux, MacOS, Windows]
Version: 0.6.5
Additional context
Add any other context about the problem here.
Would be nice to see what the SQL is being generated to understand the problem.
The text was updated successfully, but these errors were encountered:
Describe the bug
See title.
I'm using:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should just insert the numbers.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
Would be nice to see what the SQL is being generated to understand the problem.
The text was updated successfully, but these errors were encountered: