blob: A Simple S3 Class for Representing Vectors of Binary Data ('BLOBS')

Canonical link: https://rscholar.com/pkg/blob

Hadley Wickham • Kirill Müller • RStudio • View description and downloads View dependencies GitHub project

2016 Published

22 Citations

3 Authors

7 Revisions

1.2.4 Version

MIT License

Referenced by ⇅	Year
b64: Fast and Vectorized Base 64 Engine (Version 0.1.3)	2024
bigrquerystorage: An Interface to Google's 'BigQuery Storage' API (Version 1.2.2)	2024
constructive: Display Idiomatic Code to Construct Most R Objects (Version 1.1.0)	2023
nanoarrow: Interface to the 'nanoarrow' 'C' Library (Version 0.6.0)	2023
tfevents: Write Events for 'TensorBoard' (Version 0.0.4)	2023
bcputility: Wrapper for SQL Server bcp Utility (Version 0.4.3)	2021
ipaddress: Data Analysis for IP Addresses and Networks (Version 1.0.2)	2020
rapbase: Base Functions and Resources for Rapporteket (Version 1.24.0)	2019
arrow: Integration to 'Apache' 'Arrow' (Version 19.0.1)	2019
dbflobr: Read and Write Files to SQLite Databases (Version 0.2.2)	2019
dbx: A Fast, Easy-to-Use Database Interface (Version 0.3.2)	2018
flobr: Convert Files to and from Binary Objects (BLOBs) (Version 0.2.3)	2018
RMariaDB: Database Interface and MariaDB Driver (Version 1.3.4)	2017
RPostgres: C++ Interface to PostgreSQL (Version 1.4.8)	2017
dbplyr: A 'dplyr' Back End for Databases (Version 2.5.0)	2017
odbc: Connect to ODBC Compatible Databases (using the DBI Interface) (Version 1.6.0)	2017
DBItest: Testing DBI Backends (Version 1.8.2)	2016
sf: Simple Features for R (Version 1.0-19)	2016
tibble: Simple Data Frames (Version 3.2.1)	2016
bigrquery: An Interface to Google's 'BigQuery' 'API' (Version 1.5.1)	2015
DBI: R Database Interface (Version 1.2.3)	2001
RSQLite: SQLite Interface for R (Version 2.3.9)	2001

RPKG Scholar presents a tabulation of an author's contribution in the development of R packages stored in the Comprehensive R Archive Network (CRAN). Within this site, we consider package dependencies (suggests,imports,depends,enhances) as citations because we believe that using one's package to develop another is tantamount to citing the author of the package being imported, suggested or enhanced.