deepblue_query_cache {DeepBlueR} | R Documentation

## query_cache

### Description

Cache a query result in DeepBlue memory. This command is useful when the same query ID is used multiple times in different requests. The command is an advice for DeepBlue to cache the query result and there is no guarantee that this query data access will be faster.

### Usage

    deepblue_query_cache(query_id = NULL, cache = NULL,
      user_key = deepblue_options("user_key"))

### Arguments

`query_id` | - A string (Query ID)
`cache` | - A boolean (set or unset this query caching)
`user_key` | - A string (users token key)

### Value

information - A string (New query ID.)

### See Also

Other Operating on the data regions: `deepblue_aggregate`, `deepblue_binning`, `deepblue_count_regions`, `deepblue_coverage`, `deepblue_distinct_column_values`, `deepblue_extend`, `deepblue_filter_regions`, `deepblue_flank`, `deepblue_get_experiments_by_query`, `deepblue_get_regions`, `deepblue_input_regions`, `deepblue_intersection`, `deepblue_merge_queries`, `deepblue_overlap`, `deepblue_query_experiment_type`, `deepblue_score_matrix`, `deepblue_select_annotations`, `deepblue_select_experiments`, `deepblue_select_regions`, `deepblue_tiling_regions`

### Examples

    annotation_id = deepblue_select_annotations(
        annotation_name="CpG Islands",
        genome="hg19", chromosome="chr1")
    data_id = deepblue_select_experiments(
        experiment_name="E002-H3K9ac.narrowPeak.bed")
    merged_regions = deepblue_merge_queries(
        query_a_id = annotation_id,
        query_b_id = data_id)
    deepblue_query_cache(
        query_id = merged_regions, cache = TRUE)

[Package DeepBlueR version 1.14.0 Index]