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.

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

Don't print ... if number of rows is NA on input but certain after calling head() #19

Closed
krlmlr opened this issue Jan 6, 2016 · 9 comments · Fixed by #51
Closed

Don't print ... if number of rows is NA on input but certain after calling head() #19

krlmlr opened this issue Jan 6, 2016 · 9 comments · Fixed by #51
Milestone

Comments

@krlmlr
Copy link
Member

krlmlr commented Jan 6, 2016

For SQL sources.

@krlmlr krlmlr added this to the 1.0 milestone Jan 6, 2016
@krlmlr krlmlr modified the milestone: 1.0 Jan 25, 2016
@krlmlr krlmlr modified the milestones: 1.0, 2.0 Mar 2, 2016
@hadley
Copy link
Member

hadley commented Mar 18, 2016

This doesn't seem like the responsibility of tibble to me.

@hadley hadley closed this as completed Mar 18, 2016
@krlmlr
Copy link
Member Author

krlmlr commented Mar 18, 2016

Doesn't this look odd to you:

> memdb_frame(a=1)
Source:   query [?? x 1]
Database: sqlite 3.11.1 [:memory:]

       a
   (dbl)
1      1
..   ...

On the other hand, it looks to me that this would be fairly difficult to fix in dplyr in an efficient way. Would it be permissible to soften "separation of concerns" in this case?

@krlmlr
Copy link
Member Author

krlmlr commented Mar 18, 2016

Should be fixed in dplyr.

@hadley
Copy link
Member

hadley commented Mar 18, 2016

It's a bit odd, but fixing it in general is going to be fiddly, and it doesn't crop up much during real data analysis.

@krlmlr
Copy link
Member Author

krlmlr commented Mar 18, 2016

Fiddling with it right now. Parts should be fixed in tibble (trunc_mat), parts in dplyr.

Can we split up dim_desc() and export format_dim(x)?

krlmlr pushed a commit to krlmlr/dplyr that referenced this issue Mar 18, 2016
@krlmlr
Copy link
Member Author

krlmlr commented Mar 18, 2016

Now I have

> memdb_frame(a=1)
Source:   query [1 x 1]
Database: sqlite 3.11.1 [:memory:]

      a
  <dbl>
1     1

with generic dim_desc() and minor changes in dplyr.

This case occur in data analysis e.g. if you aggregate and have < 10 groups. I'd vote for reopening.

@hadley
Copy link
Member

hadley commented Mar 18, 2016

I'm willing to take a look, but I think making [1 x 1] work will break encapsulation

@krlmlr
Copy link
Member Author

krlmlr commented Mar 18, 2016

The relevant changes are #48 and krlmlr/dplyr@ae91470, works for me; I don't see where this breaks encapsulation.

@github-actions
Copy link
Contributor

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 15, 2020
krlmlr pushed a commit that referenced this issue Oct 17, 2022
* Harmonize yaml formatting

Closes #19

* revert changes to matrix section
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants