Skip to content
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.

Sign up for GitHub

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

Jump to bottom

join verb: why I do not have prefix for non-join output field? #364

Open
aborruso opened this issue Aug 31, 2020 · 3 comments
Open

join verb: why I do not have prefix for non-join output field? #364

aborruso opened this issue Aug 31, 2020 · 3 comments
Labels
feature-request

Comments

@aborruso
Copy link
Contributor

Hi,
I have these two files (input01.txt and input02.txt)

IE|1|MAYOBAN
IE|1|CORKKIN
IE|1|CORKCOR

MAYOBAN|BANGOR|2400
MAYOBEL|BELLAVARY|2400
CORKKIN|KINSALE|2200
CORKCOR|CORK|2200
DUBLD11|DUBLIN 11|2100

If I run

mlr --csv --implicit-csv-header --ifs "|" join --np --ur --ul -j 3 -l 3 -r 1 --lp l --rp r -f input01.txt input02.txt

I have the below output without any prefix.

1,2,3
MAYOBEL,BELLAVARY,2400
DUBLD11,DUBLIN 11,2100
@johnkerl
Copy link
Owner

Wow @aborruso very sorry I did not see this sooner!! :(

@johnkerl
Copy link
Owner

@aborruso unpaireds don't get the prefixing, intentionally. (Unpaired records are emitted as-found.)

Maybe they should?

@aborruso
Copy link
Contributor Author

Maybe they should?

Isn't it convenient to have an optional way to have printed what is the source of the columns? I think yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature-request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aborruso @johnkerl