Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>(edited to cover points in comments)</p> <p>To emphasise: there are differences and similarities between value-types and reference-types, but those differences have <strong>nothing</strong> to do with stack vs heap, and everything to do with copy-semantics vs reference-semantics. In particular, if we do:</p> <pre><code>Foo first = new Foo { Bar = 123 }; Foo second = first; </code></pre> <p>Then are "first" and "second" talking about the same copy of <code>Foo</code>? or different copies? It just so happens that the stack is a convenient and efficient way of <em>handling</em> value-types as variables. But that is an implementation detail.</p> <p>(end edit)</p> <p>Re the whole "value types go on the stack" thing... - value types <strong>don't</strong> always go on the stack;</p> <ul> <li>if they are fields on a class</li> <li>if they are boxed</li> <li>if they are "captured variables"</li> <li>if they are in an iterator block</li> </ul> <p>then they go on the heap (the last two are actually just exotic examples of the first)</p> <p>i.e.</p> <pre><code>class Foo { int i; // on the heap } static void Foo() { int i = 0; // on the heap due to capture // ... Action act = delegate {Console.WriteLine(i);}; } static IEnumerable&lt;int&gt; Foo() { int i = 0; // on the heap to do iterator block // yield return i; } </code></pre> <p>Additionally, Eric Lippert (as already noted) has an <a href="http://blogs.msdn.com/ericlippert/archive/2009/04/27/the-stack-is-an-implementation-detail.aspx" rel="noreferrer">excellent blog entry</a> on this subject</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy are structs stored on the stack while classes get stored on the heap(.NET)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarc Gravell
    1. USMarc Gravell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy are structs stored on the stack while classes get stored on the heap(.NET)?
      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. COThis is a great answer, but I don't think it addresses why if structs and classes are very similar, they get treated differently when it comes to the heap and the stack.
      singulars
      1. PO
      1. USichiban
    2. COI'm not sure they are "very similar" - but the point is; the differences between them have very little to do with stack and heap, and everything to do with copy-semantics vs reference-semantics
      singulars
      1. PO
      1. USMarc Gravell
    3. COEric Lippert now has another excellent and more recent blog article on the subject [The Truth About Value Types](http://blogs.msdn.com/b/ericlippert/archive/2010/09/30/the-truth-about-value-types.aspx)
      singulars
      1. PO
      1. USJustin
 

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