StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15054722
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-24T18:00:03.113
FavoriteCount
0
LastActivityDate
2013-02-24T18:27:07.157
LastEditDate
2013-02-24T18:27:07.157
LastEditorUserId
960195
OwnerUserId
960195
ParentId
15054634
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> I just want to know if i have missed or done something wrong? </blockquote> The design you're showing here is missing a few things. First, you said you want to create a generic list. How are you going to store generic data in an integer array? Also, the signature you give for <code>addItems</code> is <pre><code>public void addItems() </code></pre> and the signature you give for <code>removeItems</code> is <pre><code>public void removeItems() </code></pre> How does your list object know what to add, if it isn't given any data? Similarly, how does it know what to remove, if the client code doesn't tell it (you could always remove the first item, or always remove the last item, but then you're in stack or queue territory, not the standard object-oriented list API). I'd recommend looking at the API for <a href="http://msdn.microsoft.com/en-us/library/6sh2ey19.aspx" rel="nofollow">System.Collections.Generic.List</a>, which is the built-in class you should be trying to emulate here. You don't need to implement all the properties and methods that List implements, but you should implement parts of that API. I would recommend <pre><code>public sealed class MyList<T> { public int Count { get; } public T this[int index] { get; set; } public MyList(); public void Add(T item); public void RemoveAt(int index); } </code></pre> as the bare minimum API for a list class. You'd implement it by declaring a field of type <code>T[]</code> as the backing store, plus an internal <code>size</code> field. Don't forget that, if client code adds more items than the length of the backing store, you have to allocate a new backing store array (probably double the size of the old one), copy the elements to the new array, and start treating the new array as the backing store. You should also look into implementing <a href="http://msdn.microsoft.com/en-us/library/9eekhta0.aspx" rel="nofollow">System.Collections.Generic.IEnumerable</a>, which isn't strictly necessary, but makes a collection class much more useful.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POcreating own collection class
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USAdam Mihalcin
UserOwnerUserId
1. USAdam Mihalcin
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.