search

antonycourtney / tad

A desktop application for viewing and analyzing tabular data
http://tadviewer.com
MIT License
3.18k stars 118 forks source link

Rec column visible by default #9

Open shilman opened 7 years ago

shilman commented 7 years ago

Version: tad-0.6.1-preview Usage:

> tad top_personal_finance_commenters.csv
tad

top_personal_finance_commenters.csv.zip

antonycourtney commented 7 years ago

Thanks for reporting!

Already fixed in https://github.com/antonycourtney/tad/commit/bfa43c42a4b7675df671ae8e21471f3f10e9dfd0

I guess I better hurry up and get auto-updates working. In the meantime, a more recent snapshot is at https://www.dropbox.com/s/q81220gpd83vza1/tad-0.6.3-preview.tgz

hmontenegro commented 7 years ago

"Rec" column still visible on Tad 0.8.4

atkulp commented 5 years ago

Sorry to report "Rec" is still visible on 0.9.0

antonycourtney commented 5 years ago

Thanks for reporting. So....unlike the various internal columns (prefixed with "_" in the initial report on this issue) the additional "Rec" column is intentional. It's intended to provide a count of records (somewhat like what count(*) does in SQL), which is useful and convenient when pivoting and you want to see how many leaf rows are in each bucket. But I fully accept the feedback that the name "Rec" is pretty terrible (it was chosen for arcane historical reasons) and having it on by default is confusing and unintuitive. The right answer here is that this really should be off by default, and if the user wants it, it should be available as part of a general-purpose facility to add new columns computed from existing columns (a non-trivial effort).

XrayBravoGolf commented 6 months ago

It creates a huge confusion and undermines the trust one has in the viewer that a viewer displays exactly the data in the data file. Even if the Rec column is intended to be included, could there be a styling difference so as to highlight it as a non-data-file column but an internal column? 

cvargas-xbrein commented 1 week ago

Thanks for reporting. So....unlike the various internal columns (prefixed with "_" in the initial report on this issue) the additional "Rec" column is intentional. It's intended to provide a count of records (somewhat like what count(*) does in SQL), which is useful and convenient when pivoting and you want to see how many leaf rows are in each bucket. But I fully accept the feedback that the name "Rec" is pretty terrible (it was chosen for arcane historical reasons) and having it on by default is confusing and unintuitive. The right answer here is that this really should be off by default, and if the user wants it, it should be available as part of a general-purpose facility to add new columns computed from existing columns (a non-trivial effort).

Ok, but this could be notified before changing my data. I wasted time tracking the error in a data pipeline.

Come on, don't lose confidence in these things, it's a great program. :+1: