NA
, only prevent caching rows that have
all missing values.drop = FALSE
.dplyr::bind_rows
didn't work (instead of handing over to rbind.fill
as intended).safe_columns
is passed along in the function environment.last_cached_at
bug for existing shards.safe_column
logic to do what it actually intended.last_cached_at
column in each shard.safe_columns
, which, when TRUE will crash when (a) column tables already exist for a given cache and (b) new columns are found and added.try
blocks.dry.
parameter to cache
.double precision
types during appends, as well as
correctly setting database types upon table creation due
to RPostgres bug.real
data type,
which only supports 6 digits
of precision. This was fixed by switching these column types to
the numeric
data type.force.
.cachemeifyoucan.debug
option. Set it to true
to see the gory metadata internals of underlying postgres tables.merge2
helper that will ensure
legacy caches that have discrepancy between shards will not
truncate their output.uncached
as simply stripping the caching layer, after some
confusion as to what the correct definition should be.uncached
.cachemeifyoucan.verbose
global option for whether to display
batch caching progress.robust_batch
.force.
parameter.Integration with batchman. If a call
to a cached function procures uncached data of row count in excess that of the
parameter batch_size
to the cachemeifyoucan::cache
call, caching progress
will automatically happen in batches of batch_size
(by default 100). In other
words, data will be cached on a batch_size
record by record basis, instead
of all at once, which is very susceptible to failures.
Note this feature will only trigger if the batchman package is installed.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.