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
sqlite/chinook returns PANIC: Could not parse stored DateTime string: 2009-01-01 00:00:00: ParseError(Invalid)
on findMany()
#1763
Comments
With query generator on alpha 908 the error format changed
|
I can not confirm this any more: const { PrismaClient } = require('@prisma/client')
const prisma = new PrismaClient()
prisma.albums.findMany().then(res => {
console.log(res)
})
Can you please check if you can still confirm this @Jolg42 and/or @divyenduz? |
Fixed in latest alpha ✅ 🎊 |
I still get this error in @prisma/cli ver 2.0.0 |
@jschank Please open an new issue with a minimal reproduction. Thanks! |
I think I see the problem. When I create a new sqlite3 database using prisma and write data into the db programmatically. I can both read and write data with dates. However, when I try to generate a prisma Client using introspection of an existing database. that is where this fails. The existing database was created with typeORM and the date is written as '2020-05-31 21:11:22.000', On the other hand, prisma writes the data to the db as '1591999869569' IF anything this maybe an issue with what the introspection process decides about the data it sees. |
Yes, please open a new issue with all the information and we can take a look, reproduce and hopefully fix it @jschank. |
Hi!
|
Please open a new issue with a reproduction @MOTORIST |
chinook.db.zip
With alpha 845
The text was updated successfully, but these errors were encountered: