StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4561971
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-30T10:51:01.093
FavoriteCount
0
LastActivityDate
2010-12-30T10:51:01.093
LastEditDate
LastEditorUserId
0
OwnerUserId
245183
ParentId
4561823
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
While having the singleton accessor property within the class itself is a generally used shortcut, in more complicated situations when you need to deal with instances of multiple related classes it may prove the wrong way. The problem is mixing concerns within a single class. Your <code>MySingleton</code> class shall be rather some <code>MyClass</code> which is implemented in way generally not dependent on the number of instances that will exist on run-time. Likewise <code>MyRepository</code> shall be able to manage and provide any number of <code>MyClass</code> instances. The fact you will be dealing with only a singleton instance of <code>MyClass</code> can be encapsulated into a separate factory (or accessor or whatever you call it) class that will bind <code>MyClass</code> and <code>MyRepository</code> together. So try to rethink your design in the following way (schematic): <pre><code>public class MyClass { ... } public class MyRepository { public MyClass GetMyClassInstance(...); } public static class MyClassFactory { public static MyClass SingletonInstance { get { if (singletonInstance == null) singletonInstance = myRepository.GetMyClassInstance(...); return singletonInstance; } } } </code></pre> The remaining question is where does <code>myRepository</code> come from. For example, it can be created on program start-up and provisioned into <code>MyclassFactory</code> as a member field. At the end of the day, a lot can be made easier if you consider using an inversion of control container. The next step is also shift towards interface-based design. That gives you another layer of abstraction and provides more flexibility in terms of interchangeability of implementations.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCircular reference problem Singleton
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOndrej Tucny
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. This table or related slice is empty.
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.