Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Combine <code>attach</code> and <code>sys.source</code> to source into an environment and attach that environment. Here I have two functions in file <code>my_fun.R</code>:</p> <pre><code>foo &lt;- function(x) { mean(x) } bar &lt;- function(x) { sd(x) } </code></pre> <p>Before I load these functions, they are obviously not found:</p> <pre><code>&gt; foo(1:10) Error: could not find function "foo" &gt; bar(1:10) Error: could not find function "bar" </code></pre> <p>Create an environment and source the file into it:</p> <pre><code>&gt; myEnv &lt;- new.env() &gt; sys.source("my_fun.R", envir = myEnv) </code></pre> <p>Still not visible as we haven't attached anything</p> <pre><code>&gt; foo(1:10) Error: could not find function "foo" &gt; bar(1:10) Error: could not find function "bar" </code></pre> <p>and when we do so, they are visible, and because we have attached a <em>copy</em> of the environment to the search path the functions survive being <code>rm()</code>-ed:</p> <pre><code>&gt; attach(myEnv) &gt; foo(1:10) [1] 5.5 &gt; bar(1:10) [1] 3.027650 &gt; rm(list = ls()) &gt; foo(1:10) [1] 5.5 </code></pre> <p>I still think you would be better off with your own personal package, but the above might suffice in the meantime. Just remember the copy on the search path is just that, a <em>copy</em>. If the functions are fairly stable and you're not editing them then the above might be useful but it is probably more hassle than it is worth if you are developing the functions and modifying them.</p> <p>A second option is to just name them all <code>.foo</code> rather than <code>foo</code> as <code>ls()</code> will not return objects named like that unless argument <code>all = TRUE</code> is set:</p> <pre><code>&gt; .foo &lt;- function(x) mean(x) &gt; ls() character(0) &gt; ls(all = TRUE) [1] ".foo" ".Random.seed" </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POhiding personal functions in R
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGavin Simpson
    1. USGavin Simpson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POhiding personal functions in R
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPersonal packages are fine for this, although it still irks me that you have to jump through so many hoops to build a package. Why do I have to provide documentation for every function in a personal package?
      singulars
      1. PO
      1. USDavid Heffernan
    2. COProbably because we don't want undocumented packages on CRAN, and if R Core were to allow some checks to be by-passed, they'd have to write a whole bunch of code to allow one to install and load a deficient package. There are user tools provided to help in writing informal packages - like roxygen - so you maintain a source file (without Rd files) and generate the package files from those.
      singulars
      1. PO
      1. USGavin Simpson
    3. COAnd you don't have to document every function. Just stick an \alias{} for each function into a single help file and that should be enough to defeat the checking. You don't need \usage{} sections etc, so don't provide them. Ths trick is used quite often for internal package functions before NAMESPACES were much used.
      singulars
      1. PO
      1. USGavin Simpson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload