-
Notifications
You must be signed in to change notification settings - Fork 17
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
Need to be stricter about column compatibility in joins #168
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This was referenced May 20, 2024
Set operations are good now, joins need tidyverse/dplyr#7029. |
krlmlr
changed the title
Need to be stricter about column compatibility
Need to be stricter about column compatibility in joins
May 20, 2024
Sorry for the delayed reply. I tried generating a reprex and it didn’t error in the same way. If I can manage to reproduce, I’ll post a new issue.
Nicki Norris
Assistant Director - Data
Phone (02) 6240 8969
From: Kirill Müller ***@***.***>
Sent: Tuesday, May 21, 2024 2:48 AM
To: duckdblabs/duckplyr ***@***.***>
Cc: NORRIS,Nicki ***@***.***>; Mention ***@***.***>
Subject: Re: [duckdblabs/duckplyr] Need to be stricter about column compatibility (Issue #168)
CAUTION: This email originated from outside of the organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe.
Thanks, @nicki-dese<https://github.com/nicki-dese>, this is a different problem. Can you please open a new issue?
A reprex would be very useful. This would be a self-contained example with toy data, see, e.g., https://reprex.tidyverse.org/articles/reprex-dos-and-donts.html .
—
Reply to this email directly, view it on GitHub<#168 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APJUET37UGV7JJ4GWTEVKZLZDISNNAVCNFSM6AAAAABHZJ4TVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQHAZDENJQGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
Notice:
The information contained in this email message and any attached files may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient, any use, disclosure or copying of this email is unauthorised. If you received this email in error, please notify the sender by contacting the department's switchboard on 1300 566 046 during business hours (8:30am - 5pm Canberra time) and delete all copies of this transmission together with any attachments.
|
Done now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Also, use simple identity instead of
r_base::==
for joins.Created on 2024-05-16 with reprex v2.1.0
The text was updated successfully, but these errors were encountered: