pinsdoes not cache multiple versions… however, the different backends might. For instance, RStudio Connect always stores multiple versions, so it ought to be possible to find the correct URL from a previous version and then retrieve it with
pins. That said, it is likely the first CRAN release would not help much with versioning. Hadley asked about this as well and we have a work item tracking this: rstudio/pins#6
pinsharder to understand for its first release… So the answer is it should be possible with a bit of work. One option is to have a database board (without using RStudio Connect necessarily) which you would be able to use to pin datasets to. Then you could create a Database + RSC board which all it does is create a pin in a Database board + the RSC board, or you could store the data in the database and only store a reference to the database in the RSC board, etc. However, I think we need to first implement the Databse board to make your life easier. Another option is to get this implemented direcetly in RSC, so you don’t need to do anything but all of the sudden, pins can be queried with dplyr without having to fetch the entire dataset. Let me know when this starts to become urgent to make sure I prioritize this appropiately, my goal for now is to get the package and get some usage/feedback going, then we can spend some time improving where it makes the most sense.
.tsv.bz2files that are between 10 - 100 MB) I get the same
curlerrors as I first reported
> library(pins) > board_register(board = "github", repo = "javierluraschi/datasets", branch = "rsconf") > pin("flights.tsv", board = "github") Error in curl::form_file(path, type) : is.character(type) is not TRUE