{"action":"created","issue":{"url":"https://api.github.com/repos/JuliaStats/DataFrames.jl/issues/736","repository_url":"https://api.github.com/repos/JuliaStats/DataFrames.jl","labels_url":"https://api.github.com/repos/JuliaStats/DataFrames.jl/issues/736/labels{/name}","comments_url":"https://api.github.com/repos/JuliaStats/DataFrames.jl/issues/736/comments","events_url":"https://api.github.com/repos/JuliaStats/DataFrames.jl/issues/736/events","html_url":"https://github.com/JuliaStats/DataFrames.jl/issues/736","id":50602240,"number":736,"title":"readtable doesn't try to promote Int32 on 32bit system.","user":{"login":"adamczykm","id":5013362,"avatar_url":"https://avatars.githubusercontent.com/u/5013362?v=3","gravatar_id":"","url":"https://api.github.com/users/adamczykm","html_url":"https://github.com/adamczykm","followers_url":"https://api.github.com/users/adamczykm/followers","following_url":"https://api.github.com/users/adamczykm/following{/other_user}","gists_url":"https://api.github.com/users/adamczykm/gists{/gist_id}","starred_url":"https://api.github.com/users/adamczykm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adamczykm/subscriptions","organizations_url":"https://api.github.com/users/adamczykm/orgs","repos_url":"https://api.github.com/users/adamczykm/repos","events_url":"https://api.github.com/users/adamczykm/events{/privacy}","received_events_url":"https://api.github.com/users/adamczykm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2014-12-02T01:36:17Z","updated_at":"2016-05-25T22:33:38Z","closed_at":null,"body":"As in title. I got a column with some big values - unix timestamps. The readtable function converts them to Int32, leaving me with negative values. It might be really troublesome when unnoticed. It doesn't even warn."},"comment":{"url":"https://api.github.com/repos/JuliaStats/DataFrames.jl/issues/comments/221727903","html_url":"https://github.com/JuliaStats/DataFrames.jl/issues/736#issuecomment-221727903","issue_url":"https://api.github.com/repos/JuliaStats/DataFrames.jl/issues/736","id":221727903,"user":{"login":"davidanthoff","id":1036561,"avatar_url":"https://avatars.githubusercontent.com/u/1036561?v=3","gravatar_id":"","url":"https://api.github.com/users/davidanthoff","html_url":"https://github.com/davidanthoff","followers_url":"https://api.github.com/users/davidanthoff/followers","following_url":"https://api.github.com/users/davidanthoff/following{/other_user}","gists_url":"https://api.github.com/users/davidanthoff/gists{/gist_id}","starred_url":"https://api.github.com/users/davidanthoff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidanthoff/subscriptions","organizations_url":"https://api.github.com/users/davidanthoff/orgs","repos_url":"https://api.github.com/users/davidanthoff/repos","events_url":"https://api.github.com/users/davidanthoff/events{/privacy}","received_events_url":"https://api.github.com/users/davidanthoff/received_events","type":"User","site_admin":false},"created_at":"2016-05-25T22:33:38Z","updated_at":"2016-05-25T22:33:38Z","body":"We just ran into this issue: we read a CSV file that has one column that has some very large integer numbers in it, too large for an ``Int64``. The current behavior is really a bug, i.e. ``readtable`` just tries to read these into ``Int64``s, overflows and doesn't even warn about this.\r\n\r\nI can see three alternative behaviors, and each one of these would be preferable:\r\n1. Properly detect the type, if the numbers e.g. would fit into a ``Int128`` just use that as the type\r\n2. Use ``String`` as the datatype. At least there is no data loss/corruption in that case\r\n3. Give a warning. Not great, but at least it would alert people that there was a data corruption."}}
{"actor":{"display_login":"davidanthoff"}}