Otto Fajardo
Otto Fajardo
Thanks for the report. The issue can also be seen if you read the resulting file with pyreadstat and look at meta.original_variable_types, meaning that the format is not correctly set,...
I am afraid you are mixing things up. What you are looking at is the length of the string itself, which has to be calculated in order for the C...
maybe, but if the bug is in Readstat (and I think it is), it should be fixed there and not worked around here in pyreadstat.
@maver1ck just for the records, I tried you proposed work around and unfortunately it does not solves the issue. Therefore the only possibility is to wait for it to be...
write_dta:A provided string value was longer than the available storage size of the specified column
hi, thanks for the report. Please provide the data to reproduce the problem as indicated in the template.
write_dta:A provided string value was longer than the available storage size of the specified column
in order to make the issue reproducible, please provide dtype_dict ( and any other information necessary to reproduce)
write_dta:A provided string value was longer than the available storage size of the specified column
OK, it seems that the issue is that you have one specific row with a very long string (of length 1988). Right now pyreadstat is writing it as dta type...
write_dta:A provided string value was longer than the available storage size of the specified column
solved in version 1.2.9
Hi, thanks for the report. Unfortunately the underlying C library does not support writing columns with objects other than the simple types (integer, double, character, ... See the complete list...
As a suggestion, in R, modify the character to the syntax of a vector (replace [ with c(, etc), and do an eval.