Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Update: <code>@expose</code> is now deprecated. Answer updated with new method.</strong></p> <p>As you noted, <code>@const</code> has no impact on inlining. <code>@const</code> only means that the value doesn't change (is assigned/set only once).</p> <p><code>@nocollapse</code> was specifically created to prevent property collapsing. Given:</p> <pre><code>goog.provide('foo.bar'); /** @nocollapse */ foo.bar.baz = 42; alert(foo.bar.baz); </code></pre> <p>The purpose of <code>@nocollapse</code> in this case is to prevent the compiler from collapsing the property to something like:</p> <pre><code>var a = 42; alert(a); </code></pre> <p>However the compiler still knows from flow analysis that <code>foo.bar.baz</code> is assigned the integer <code>42</code> and never changed. Therefore it's going to just use the known values.</p> <p>The only reliable way to prevent inlining is to export the property:</p> <pre><code>goog.provide('foo'); goog.provide('foo.bar'); foo.bar.baz = 42; goog.exportProperty(foo.bar, 'baz', foo.bar.baz); alert(foo.bar.baz); </code></pre> <p>There is a known (albeit small) need to stipulate to the compiler that renaming is safe, but inlining is not. See <a href="https://code.google.com/p/closure-compiler/issues/detail?id=971" rel="nofollow">https://code.google.com/p/closure-compiler/issues/detail?id=971</a></p> <p>If you are not using closure library, the export would look like this:</p> <pre><code>var foo = {}; foo.bar = {}; /** @nocollapse */ foo.bar.baz = 42; foo.bar['baz'] = foo.bar.baz; alert(foo.bar.baz); </code></pre> <p>If your goal is to make sure <code>foo.bar.baz</code> isn't inlined OR renamed, then you would need either quoted properties and <code>@nocollapse</code>.</p> <pre><code>goog.provide('foo'); goog.provide('foo.bar'); /** @nocollapse */ foo.bar.baz = 42; goog.exportProperty(foo.bar, 'baz', foo.bar.baz); alert(foo.bar.baz); </code></pre> <p>If you are providing this namespace to others for use, then the best case is a combination of <code>@nocollapse</code> to prevent collapsing and allow external updating and <code>goog.exportSymbol</code>.</p> <pre><code>goog.provide('foo'); goog.provide('foo.bar'); /** @nocollapse */ foo.bar.baz = 42; goog.exportSymbol('foo', foo); goog.exportProperty(foo, 'bar', foo.bar); goog.exportProperty(foo.bar, 'baz', foo.bar.baz); alert(foo.bar.baz); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POPreventing inlining of exported properties as constants w/ Google Closure Compiler
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChad Killingsworth
    1. USChad Killingsworth
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPreventing inlining of exported properties as constants w/ Google Closure Compiler
      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. VTAcceptedByOriginator
    1. COThanks for the suggestions, but I've already tried the `exportProperty` usage you suggest. Trying it again just now via the compiler service (just to be sure), [the results are not desirable](https://gist.github.com/cemerick/7371885): `baz` is no longer present at all. To be clear, the objective is to expose `baz` to users of the output that have not participated in the compilation, and allow their modifications of `baz` to be reflected in `quux`.
      singulars
      1. PO
      1. UScemerick
    2. COThat's a different problem - and you can clearly see that `foo.bar.baz` was NOT inlined (but it was renamed). If you want to prevent renaming, you'll neeed to introduce either `@expose` annotations or use quoted properties. I've updated the answer accordingly.
      singulars
      1. PO
      1. USChad Killingsworth
    3. COEdited to include some working code that exports each symbol leading to the `@expose`d property. Chad, this varies from your suggestion somewhat; `exportProperty` for `foo.bar` did not yield good results. I'm curious why, but at this point, I'm happy to have something working. Any final thoughts before I accept the answer?
      singulars
      1. PO
      1. UScemerick
 

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