-
Notifications
You must be signed in to change notification settings - Fork 977
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
fread/fwrite *base data types* directly for efficiency #1656
Comments
It would be awesome if |
@clarkdk You discuss quite a different issue, as it requires parsing strings that stores date/datetime. This issue is about date/datetime stored as numerics, and those can be effectively optimized for IO speed if fwrite and fread would be able to write and read those types as their numerics transparently (or using just |
@jangorecki OK, now I understand. I will make a separate FR. In implementing datetimes as numerics in |
now when have yaml support this feature is even more useful as we can maximise IO without trade-offs |
Not sure if this belongs to this issue or to 3391 or to the master task 2247, but I could reproduce an unexpected behavior with
See: https://stackoverflow.com/questions/58493926/fread-with-yaml-true-read-type-date-as-character |
@PavoDive could you file a new issue for that? please & thank you |
There could be an option for
fwrite
andfread
to dump/read the unclassed representation of objects. In such a case whole IO process can be much faster, because we don't have to formatPOSIXct
,[I]Date
and other classes for writing to file, we justunclass
them, and write numbers (or any other base type they use) to a file. Later when reading withfread
we providecolClasses
(oryaml
), and those numbers (or another base types) are properly recognized as their original class.The text was updated successfully, but these errors were encountered: