appendDataset

dataset1

another CrunchDataset, or possibly a data.frame. If
<code>dataset2</code> is not a Crunch dataset, it will be uploaded as a new
dataset before appending.

dataset2

logical: should the user be forced to review and accept
any automatically resolved conflicts between <code>dataset1</code> and
<code>dataset2</code>? Defaults to <code>TRUE</code> when occurring in an interactive
R session, <code>FALSE</code> otherwise. I

confirm

logical: if the append operation fails or is aborted, should
the intermediate batch created on <code>dataset1</code> be deleted? Default is
<code>TRUE</code>; <code>FALSE</code> may be useful if you want to review the append
conflicts in the web applicati

cleanup

The Crunch.io service (http://crunch.io/) provides a cloud-based
    data store and analytic engine, as well as an intuitive web interface. 
    Using this package, analysts can interact with and manipulate Crunch
    datasets from within R. Importantly, this allows technical researchers to
    collaborate naturally with team members, managers, and clients who prefer a
    point-and-click interface.

appendDataset: Append one Crunch dataset to another

Description

Usage

Arguments

Value