joins are one of the biggest causes of data quality and integrity issues in the data space.
Re:Tidyverse 2.0.0
by VeninVidiaVicii on Sunday April 09, 2023 @11:26AM
(#35503615)
Yeah maybe, but chaining a bunch of joins together when exploring some new data is a thing I do all the time. Then, 4-5 warnings push my results off the screen. It’s infuriating.
Re:Tidyverse 2.0.0
by naijaboiler on Sunday April 09, 2023 @02:44PM
(#35505309)
I avoid joins in R like a plague. Been burned. If I am working with a finite number of colummns, I just use base R match and add column by column. yes it breaks DRY but I don't get weird surprises. and I can re-run any section of the code at any time from any point without breaking things or joining the same and creating unintended duplicate columns
Re:Tidyverse 2.0.0
by victorbohr on Sunday April 09, 2023 @03:10PM
(#35505517)
Take a look at the powerjoin package. It let's you specify strict rules for your joins, for example requiring unique keys in the right-side table when doing a left join. It's got some other neat features as well.
Re:Tidyverse 2.0.0
by LaserPineapple on Sunday April 09, 2023 @02:55PM
(#35505385)
What kind of weird surprises have you run into? Are they specific to R?
One issue I've noticed is the increasing frequency of warnings, such as when performing left or inner joins. These warnings can be a bit overwhelming at times.
However, it's worth noting that you can suppress these warnings by using the "multiple='all'" parameter, which is easy to fumble when you’re exploring data, why not simply "all=TRUE”? It seems like a lack of ergonomics and considering user experience.