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

Uploading an R object w/o writing to file #44

Closed
jennybc opened this issue May 22, 2017 · 4 comments
Closed

Uploading an R object w/o writing to file #44

jennybc opened this issue May 22, 2017 · 4 comments

Comments

@jennybc
Copy link
Member

jennybc commented May 22, 2017

In testing, I note its awkward to always have to write to file before uploading. We need to offer a way to upload from an R object directly to Drive.

@LucyMcGowan LucyMcGowan self-assigned this Jun 13, 2017
@jennybc jennybc added the future label Aug 14, 2017
@sanjmeh
Copy link

sanjmeh commented Feb 16, 2018

a gentle reminder that this is still open.
One more reason why writing to a file first is a bad idea is because the NAs are all lost. Also sometimes extra quotes are inserted that need cleaning. Thanks

@jennybc
Copy link
Member Author

jennybc commented Jun 21, 2021

I can't convince myself this is needed. To implement, you have to have specific combinations of R object and destination file type in mind. The most common one would be a data frame and Sheet, but that's what googlesheets4 is for. Closing until a specific use case presents itself.

@renatocava
Copy link

I can't convince myself this is needed. To implement, you have to have specific combinations of R object and destination file type in mind. The most common one would be a data frame and Sheet, but that's what googlesheets4 is for. Closing until a specific use case presents itself.

Hello @jennybc, a necessity is when you want to use Google Drive to store backup copies that are created daily, then an RDS or CSV file will take up less space than a GOOGLESHEET. Any recommendation?

@jennybc
Copy link
Member Author

jennybc commented Feb 16, 2024

@renatocava In general, closed issues aren't a good place for discussion. If you're really interested in this, you should open a new issue and, in this case, provide some concrete details about the size differences you observe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants