deschen1

Results 43 comments of deschen1

read_sav fails if two string variable names are exactly 5 characters + one digit

I think I can confirm this issue with my data set when trying to read in data with `read_sav`. Having my original variable names being `QB5B_1` and `QB5B_2`, readin in...

read_sav fails if two string variable names are exactly 5 characters + one digit

Just wondering, is this bug already fixed now in ReadStat and is the bugfix also implemented in haven now? I'm asking because I came across this very unfortunate bug again...

Handle invalid multi-byte sequences in iconv encoding conversions

Sorry for nudging...just curious about this bug and its fix, since it's been quite for some time now. I got hit again by the "invalid byte sequence" bug for another...

read_Sav regression "Unable to convert string to the requested encoding (invalid byte sequence)"

I have the same issue (same error message) with one of my data sets. I didn't understand all of what was said above, but wanted to check if there's a...

read_Sav regression "Unable to convert string to the requested encoding (invalid byte sequence)"

Thanks for the update nonetheless. And thanks for working on this bug/issue.

read_Sav regression "Unable to convert string to the requested encoding (invalid byte sequence)"

FWIW, I have opened a bug report in SPSS, just in case they might have been able to do sth. about the beahviour. Here's their response. Not sure if it...

`rows_*()` functions should be able to use different joins keys in `x` and `y`

The use case is when having different by names in the two data frames, x and y. In the example I want to match a1 from x with a2 from...

`rows_*()` functions should be able to use different joins keys in `x` and `y`

That's what I usually end up doing, yes. But a named vector like in join functions feels programmatically cleaner and less workaroundy.

`rows_*()` functions should be able to use different joins keys in `x` and `y`

Sure, I just had one use case yesterday. Let's assume I have three data sets: ``` df1

Header passing fails with header that starts with HTTP_

Not sure if of any help. But today I got the exact same warning for another API (Caplena - non-public, so can't share any reprex) that is new, i.e. it...