[v2] Postgres: date/time field value out of range
See original GitHub issueI’ve added Postgres as the database adapter. When I try to log in with an OAuth provider I get the error below. The user and account records are created without errors only the session is missing.
Create session for user User {
name: 'Sproettiemao',
email: 'lori.karikari@gmail.com',
image: null,
id: 1
}
(node:2317) UnhandledPromiseRejectionWarning: QueryFailedError: date/time field value out of range: "1591612180339"
at new QueryFailedError (/home/lori/dev/my-eui-starter/node_modules/typeorm/error/QueryFailedError.js:11:28)
at Query.callback (/home/lori/dev/my-eui-starter/node_modules/typeorm/driver/postgres/PostgresQueryRunner.js:176:38)
at Query.handleError (/home/lori/dev/my-eui-starter/node_modules/pg/lib/query.js:146:19)
at Connection.connectedErrorMessageHandler (/home/lori/dev/my-eui-starter/node_modules/pg/lib/client.js:236:17)
at Connection.emit (events.js:315:20)
at Socket.<anonymous> (/home/lori/dev/my-eui-starter/node_modules/pg/lib/connection.js:121:12)
at Socket.emit (events.js:315:20)
at addChunk (_stream_readable.js:297:12)
at readableAddChunk (_stream_readable.js:273:9)
at Socket.Readable.push (_stream_readable.js:214:10)
at TCP.onStreamRead (internal/stream_base_commons.js:186:23)
(node:2317) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
PostgresSQL date/time field out of range on seconds-since ...
I am importing a csv file into a PostgreSQL ...
Read more >ERROR: date/time field value out of range: "1658792421"
I'm trying to convert and epoch to a string on PostgreSQL and I get the following error:
Read more >Date/time field value out of range, need a different "datestyle ...
Hi All,. I encountered the following error when using Custom SQL Query with PostgreSQL connector connecting to a db. Unexpected Error.
Read more >[v2] Postgres: date/time field value out of range #104 - GitHub
I've added Postgres as the database adapter. When I try to log in with an OAuth provider I get the error below. The...
Read more >Error “date/time field out of range” occurs for MDY date style
Error “date/time field value out of range: "12/30/2018"(Hint Perhaps you need a different "datestyle" setting.;” occurs, when the generated SQL ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, it works now 🎉. I wanted to take a look at it but didn’t really have any time today. But I was thinking of going the ISOString route too.
I think this might be addressed in beta 13 which was just pushed to
next-auth@beta
.If you try it out would appreciate any feedback!