Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rstudio/pool
Object Pooling in R
https://github.com/rstudio/pool
Last synced: 3 months ago
JSON representation
Object Pooling in R
- Host: GitHub
- URL: https://github.com/rstudio/pool
- Owner: rstudio
- License: other
- Created: 2016-05-18T17:33:18.000Z (over 8 years ago)
- Default Branch: main
- Last Pushed: 2024-03-08T15:59:26.000Z (8 months ago)
- Last Synced: 2024-06-19T01:57:45.409Z (5 months ago)
- Language: R
- Homepage: http://rstudio.github.io/pool/
- Size: 4.69 MB
- Stars: 243
- Watchers: 21
- Forks: 30
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-shiny-extensions - pool - Database connection pooling in R. (Backend / Database)
- jimsghstars - rstudio/pool - Object Pooling in R (R)
README
pool
====
[](https://github.com/rstudio/pool/actions/workflows/R-CMD-check.yaml)
[](https://github.com/rstudio/pool/actions)
[](https://app.codecov.io/gh/rstudio/pool?branch=main)
The goal of the **pool** package is to abstract away the challenges of database connection management, which is particularly relevant in interactive contexts like Shiny apps that connect to a database.
Instead of creating and closing connections yourself, you create a "pool" of connections, and the pool package manages them for you. You never have to create or close connections directly: The pool knows when it should grow, shrink or keep steady. You only need to close the pool when you’re done. The pool works seamlessly with DBI and dplyr, so in most cases using the pool package is as simple replacing `DBI::dbConnect()` with `dbPool()` and adding a call to `poolClose()`.
Learn more about why pool is needed in `vignette("why-pool")`.
(The pool package is actually general enough to allow you to construct a pool of any kind of object, not just database connections, but database connections are currently its primary claim to fame.)
## Usage
Here’s a simple example of using a pool within a Shiny app (feel free to try it yourself):
```r
library(shiny)
library(dplyr)
library(pool)
loadNamespace("dbplyr")
pool <- dbPool(
drv = RMySQL::MySQL(),
dbname = "shinydemo",
host = "shiny-demo.csa7qlmguqrf.us-east-1.rds.amazonaws.com",
username = "guest",
password = "guest"
)
onStop(function() {
poolClose(pool)
})
ui <- fluidPage(
textInput("ID", "Enter your ID:", "5"),
tableOutput("tbl"),
numericInput("nrows", "How many cities to show?", 10),
plotOutput("popPlot")
)
server <- function(input, output, session) {
city <- tbl(pool, "City")
output$tbl <- renderTable({
city |> filter(ID == !!input$ID) |> collect()
})
output$popPlot <- renderPlot({
df <- city |> head(input$nrows) |> collect()
pop <- df |> pull("Population", name = "Name")
barplot(pop)
})
}
shinyApp(ui, server)
```
Note: the `loadNamespace("dbplyr")` line is there to help the [rsconnect](https://github.com/rstudio/rsconnect) package when deploying the application to [shinyapps.io](https://www.shinyapps.io/) or [Posit Connect](https://posit.co/products/enterprise/connect/). Without that line, rsconnect will not detect that the dbplyr package is needed, and the application will not work properly.