Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The way postback works in .NET is actually a wrapper around the more basic idea of HTML forms. A basic example of HTML forms is:</p> <pre><code>&lt;html&gt; &lt;body&gt; &lt;form action="" method="POST"&gt; &lt;input type="text" value="type here" /&gt; &lt;input type="submit" value="go" /&gt; &lt;/form&gt; &lt;/body&gt; &lt;/html&gt; </code></pre> <p>Roughly, what the .NET abstraction adds is:</p> <pre><code>&lt;html&gt; &lt;body&gt; &lt;form action="" method="POST"&gt; &lt;input type="hidden" name="__VIEWSTATE" value="string-encoded-value" /&gt; &lt;input type="text" name="bob" value="type here" /&gt; &lt;input type="submit" value="go" /&gt; &lt;/form&gt; &lt;/body&gt; &lt;/html&gt; </code></pre> <p>Whereby on postback to your page, all input elements with names are mapped back into properties of your Page object, and the <code>__VIEWSTATE</code> hidden field is deserialized into all properties of objects that do not correspond to values of html <code>input</code> tags. For example, if <code>Page.bob</code> had a <code>DateTime</code> property associated with it, it would be stored in <code>__VIEWSTATE</code> possibly.</p> <p>ASP.NET <code>Literal</code> tags in Page markup will get printed into the browser exactly as is, meaning that if you have <code>&lt;span&gt;bob&lt;/span&gt;</code> as its value, that is how it will appear within the <code>&lt;form&gt;</code> tag. However, in plain HTML world, <code>&lt;form&gt;</code> tags when posted will only contain the values of certain form elements (aka not every <code>div</code>, <code>span</code>, <code>p</code> etc. gets posted back, only <code>input</code>, <code>select</code>, <code>textarea</code> and some others). So if your literal doesn't contain an <code>input</code> then it won't even get posted back meaning <code>__VIEWSTATE</code> will be used to restore the <code>Value</code> property of the <code>Literal</code> back to its initial state.</p> <p>To fix this, you probably don't want to stick html into a <code>Literal</code> because even if you do it's not clear that it will get associated with the right property of your page. Instead, try a <code>TextBox</code> element or something else that gets written as an <code>input</code> element directly by the ASP.NET webforms code. Alternatively, try using javascript to allow modifications of flat text in divs if you don't need to persist the data.</p>
    singulars
    1. This table or related slice is empty.
    1. POASP (.NET 4) ViewState enabled Literal control not retaining changes to HTML contents on PostBack
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USwelegan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POASP (.NET 4) ViewState enabled Literal control not retaining changes to HTML contents on PostBack
      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. VTAcceptedByOriginator
    1. COWell that's good to know (+1), but the HTML I'm interested in capturing actually is the contents of `<input>` tags, so I'm still confused. Is there a way to associate my `<input>` tags in the database with the correct form used for PostBack?
      singulars
      1. PO
      1. UShatch22
    2. COThe entire page is one form tag, so on postback, odds are that your `Request.Form["input-name-value"]` property contains what you are looking for. But rather than manually extracting that value from the `Form` collection, you should use a `TextBox` instead of `Literal` and it will automatically get tied to a property in your user control
      singulars
      1. PO
      1. USwelegan
    3. COAKA `<ItemTemplate><asp:TextBox ID="litRowData" runat="server" EnableViewState="true"></asp:TextBox></ItemTemplate>` and `litRowData.Value = HTMLData`
      singulars
      1. PO
      1. USwelegan
 

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