Databases
StackOverflow2013
Postsdbo
POViewState - proper way to store data in collections
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POViewState - proper way to store data in collections
    primarykey
    data
    text
    <p>Assume I have a collection of objects</p> <pre><code>List&lt;MyClass&gt; collection = new List&lt;MyClass&gt;(); </code></pre> <p>And a dictionary where these objects will be inserted</p> <pre><code>Dictionary&lt;string, List&lt;MyClass&gt;&gt; sections = new Dictionary&lt;string, List&lt;MyClass&gt;&gt;(); // example of insertion sections["A"].Add(collection[2]); </code></pre> <p>List and dictionary are stored in a <code>ViewState</code>. Will it be more memory-friendly to store identifiers of objects in the dictionary and bind them with objects later, when I need them?</p> <pre><code>Dictionary&lt;string, List&lt;int&gt;&gt; sections = new Dictionary&lt;string, List&lt;int&gt;&gt;(); // example of insertion sections["A"].Add(collection[2].ID); </code></pre> <p>As I understand there will be no performance boost because in the first case dictionary will contain references which are 32/64 bits in size. Is it true?</p> <p><strong>EDIT</strong></p> <p><code>MyClass</code> is a class, not a struct. List and Dictionary are declared like this:</p> <pre><code>private List&lt;MyClass&gt; A { get { if (ViewState["a"] == null) { ViewState["a"] = // retrieve data from db } return (List&lt;MyClass&gt;)ViewState["a"]; } set { ViewState["a"] = value; } } private Dictionary&lt;string, List&lt;MyClass&gt;&gt; B { get { if (ViewState["b"] == null) { ViewState["b"] = new Dictionary&lt;string, List&lt;MyClass&gt;&gt;(); } return (Dictionary&lt;string, List&lt;MyClass&gt;&gt;)ViewState["b"]; } set { ViewState["b"] = value; } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChruS
    1. USChruS
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POViewState - proper way to store data in collections
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POViewState - proper way to store data in collections
      1. This table or related slice is empty.
      1. VTUpMod
    1. COyes, if `MyClass` is a `class`, not a `struct`
      singulars
      1. POViewState - proper way to store data in collections
      1. USIlya Ivanov
    2. COWhere are you keeping your objects? They will be destroyed after your page has been sent to the client, so even though you are keeping references to them in your viewstate, they won't point to anything valid on your return trip. So, you more than likely need to keep them in session, and once you have them in session, there really isn't a need to have anything in your viewstate to reference them.
      singulars
      1. POViewState - proper way to store data in collections
      1. USAaronS
    3. COModified my post.
      singulars
      1. POViewState - proper way to store data in collections
      1. USChruS
 

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