Skip to content
New issue

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

SQLCODE: 22008 SQLERROR: ERROR: date/time field value out of range: "0000-00-00 00:00:00" #16

Closed
ghost opened this issue Jul 24, 2017 · 2 comments
Assignees
Milestone

Comments

@ghost
Copy link

ghost commented Jul 24, 2017

Is there a way to "transform" those?

Jul 24 13:55:39: [ERROR] - pg_lib.py (510): b'INSERT INTO "cpc"."meta_config" ("id","key","value","created_at","updated_at") VALUES (\'1\',\'payment_overdue_limit\',\'30\',\'0000-00-00 00:00:00\',\'0000-00-00 00:00:00\');'

I understand that it should look like this:

insert into subscriptions_sub(datetime_created) values (NULLIF(your_field_name,'0000-00-00 00:00:00')::timestamp)

to be totally safe...

@the4thdoctor
Copy link
Owner

The row image doesn't carry informations about the data type. Maybe querying the postgres system catalogue when the procedure starts the replay can fix this sort of issues. I'm adding this enhanchement tentatively to the version 1.7 (currently working on the 1.6) as this require time to be correctly addressed.

@the4thdoctor the4thdoctor added this to the Version 1.7 milestone Jul 25, 2017
the4thdoctor added a commit that referenced this issue Aug 23, 2017
setup for field_functions which will solve the issue #16
@the4thdoctor
Copy link
Owner

I've wrongly addressed the issue 22 in the last commit. However the fix for this issue will appear in the upcoming version 1.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant