You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently have the problem that a csv file with the following input:
2012-08-11
Will get converted and returned as:
2012-08-11T00:00:00
The basic issue is that we don't get a sense of precision.
There are several options:
Guess type but do not use this for parsing (bad IMO because we don't convert thursday 25th january to something standard - though this could be a good thing ??)
Leave it to clients to strip unnecessary precision
Do a hack to strip T00:00:00 style stuff from all dates when do serialization to json ...
The text was updated successfully, but these errors were encountered:
Right but it is sort of unexpected and leads to data changing from it source - e.g. i see 2012-08-01 in the csv source but end up with 2012-08-01 00:00:00 or similar ...
Currently have the problem that a csv file with the following input:
Will get converted and returned as:
The basic issue is that we don't get a sense of precision.
There are several options:
The text was updated successfully, but these errors were encountered: