Skip to content
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

delimiter error for json type data #37

Closed
hcheng2002cn opened this issue May 1, 2021 · 4 comments · Fixed by #41
Closed

delimiter error for json type data #37

hcheng2002cn opened this issue May 1, 2021 · 4 comments · Fixed by #41

Comments

@hcheng2002cn
Copy link

we have attached file, clevercsv guess delimiter ':', instead of ','
The three data type are json, time without time zone and time with time zone.

"{""fake"": ""json"", ""fake2"":""json2""}",13:31:38,06:00:04+01:00
"{""fake"": ""json"", ""fake2"":""json2""}",22:13:29,14:20:11+02:00
"{""fake"": ""json"", ""fake2"":""json2""}",04:37:27,22:04:28+03:00
"{""fake"": ""json"", ""fake2"":""json2""}",04:25:28,23:12:53+01:00
"{""fake"": ""json"", ""fake2"":""json2""}",21:04:15,08:23:58+02:00
"{""fake"": ""json"", ""fake2"":""json2""}",10:37:03,11:06:42+05:30
"{""fake"": ""json"", ""fake2"":""json2""}",10:17:24,23:38:47+06:00
"{""fake"": ""json"", ""fake2"":""json2""}",00:02:51,20:04:45-06:00

Would you please help to take a look ?

Thanks
hong

@hcheng2002cn
Copy link
Author

hcheng2002cn commented May 1, 2021

@Giovanni1085 attached is data type we think might occur at csv files:
Number:

  • Big Int: 4956257178188190255, -4317065446001561192
  • Int: 1313186727, -590456576
  • small int: -9875, 1992
  • double_precision: -37482301.4311, 94631296444848.6

Text: 'ScBiSTZZXkjuRWQUnTze'
Char: 'a'

Bool: False, True
Date: '2014-08-15'
time_no_zone: '19:38:12'
time_with_zone: '05:14:35+01:00'
timestamp_no_zone: '2007-04-14T06:00:53'
timestamp_with_zone: '1973-11-12T05:14:35+01:00'
json: "{""fake"": ""json"", ""fake2"":""json2""}"

@hcheng2002cn
Copy link
Author

for recognized type, can we differentiate the score ? since basic everything can be detect as text, and time/timestamp ... is more precise.

Thanks

GjjvdBurg added a commit that referenced this issue Jul 16, 2021
* Add a JSON object data type to address a specific failure case ([#37](#37)).
* Add support for timezones for time data type
* Add support for building wheels on non-native architectures ([#39](#39)).
* Add a flag to disable skipping type detection using the command line interface.
@GjjvdBurg
Copy link
Collaborator

Apologies for the slow response on this @hcheng2002cn! This has now been fixed in CleverCSV version 0.7.0.

@hcheng2002cn
Copy link
Author

thanks for fix ! will try out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants