Databases
StackOverflow2013
Postsdbo
POMVC 3 Simple Inheritance
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMVC 3 Simple Inheritance
    primarykey
    data
    text
    <p>I have come across a situation where the answer should be really straight forward, but it eludes me.</p> <pre><code>public class Note { #region Properties public int Id { get; set; } public int ClientId { get; set; } public int CandidateId { get; set; } public int TypeId { get; set; } public DateTime DateCreated { get; set; } public string UserId { get; set; } public string UserName { get; set; } public string Message { get; set; } #endregion #region Methods public void Save() { } #endregion } public class History : Note { } </code></pre> <p>As you can see, History inherits Note. They are exactly the same, the only difference between the two is the type Id.</p> <p>I have this function when getting data from the database</p> <pre><code> public static Note Parse(SqlDataReader dr) { int TypeId = Convert.ToInt32(dr["TypeId"]); Note Note; if (TypeId == 1) Note = new Note(); else Note = new History(); Note.Id = Convert.ToInt32(dr["Id"]); Note.TypeId = TypeId; if (dr["ClientId"] != DBNull.Value) Note.ClientId = Convert.ToInt32(dr["ClientId"]); if (dr["CandidateId"] != DBNull.Value) Note.CandidateId = Convert.ToInt32(dr["CandidateId"]); Note.DateCreated = Convert.ToDateTime(dr["DateCreated"]); Note.UserId = Convert.ToString(dr["UserId"]); Note.UserName = Convert.ToString(dr["UserName"]); Note.Message = Convert.ToString(dr["Message"]); return Note; } </code></pre> <p>And then on my MVC page I have this:</p> <pre><code>&lt;ol id="interview-comments"&gt; @foreach (Note Note in Model.Notes().OfType&lt;Note&gt;()) { } &lt;/ol&gt; &lt;ol id="history-comments"&gt; @foreach (History Note in Model.Notes().OfType&lt;History&gt;()) { } &lt;/ol&gt; </code></pre> <p>My question is simple. Is this the correct way to do it?</p> <p>/r3plica</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStereško
    1. USr3plica
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COLike the answers say, you probably should _not_ do it this way. In general I find that inheritance can bite you, so I tend to stay away from it if possible.
      singulars
      1. POMVC 3 Simple Inheritance
      1. USTim Hobbs
    2. CO@jesus.tesh, it's not necessary to "stay away" from inheritance IMHO, but use it only when appropriate. Don't use a screwdriver to hammer in a nail... ;)
      singulars
      1. POMVC 3 Simple Inheritance
      1. USLucero
    3. CO@Lucero - sure, I wasn't claiming inheritance should not be used. Use the right tool for the job, right? :)
      singulars
      1. POMVC 3 Simple Inheritance
      1. USTim Hobbs
 

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