-
Notifications
You must be signed in to change notification settings - Fork 103
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
Requirement of tryParseDateTime
etc not mentioned in documentation
#281
Comments
for now, paste the following code into your model.dart
|
When I insert this line in my code: When viewing the database, it saves the following value in the column of type "DateTime": But if I enter the following code: It works! However, I found this update a little strange. I work with receiving Json info where dates are saved in milliseconds correctly. I want to save iso in milliseconds and read the value in milliseconds converting to DateTime without formatting the date to String. |
It's @a7mdragab 's work. We can take back that change if it affects db badly |
If it is possible to always save the information in milliseconds and later just read them using these "date formats" in my case it would solve it. Until they make a decision about the future of this package, I will downgrade the version I use in my project. |
I have no idea why the default behavior was changed without documentation. @GoedertDalmolin This is what I ended up doing so the old milliseconds since epoch would work:
|
Hi @JWambaugh. I wanted to thank you from the bottom of my heart!} This worked for me. I use this package in a production application that has clients, and I decided to update to the latest version. Unfortunately I came across this situation that you commented, where there is no documentation for such a big change. I hope they don't make decisions like that again. Add "parse" method by updating your code @JWambaugh:
|
Hi all,
If someone wants to use DefaultDateTime format, must specify the sqfentity_gen version in pubspec.yaml |
Builds now fail unless these functions are defined in the model, yet there's no mention of them in the documentation:
The text was updated successfully, but these errors were encountered: