StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7794006
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-17T12:51:33.933
FavoriteCount
0
LastActivityDate
2011-10-17T12:51:33.933
LastEditDate
LastEditorUserId
0
OwnerUserId
66686
ParentId
7793707
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
There are a couple of reasons why you should do this. Some good. Some bad. Lets start with a bad reason: <ul> <li>Because everybody says so. Your coworker really should be able to explain why and you should ask him. Then judge his reasons.</li> </ul> A Better reason: It really boils down to the single responsibility principle (the S of <a href="http://en.wikipedia.org/wiki/SOLID_%28object-oriented_design%29" rel="nofollow">SOLID</a>) If you have a class A and that instantiates a class B and calls that instance it really is a strong hint that you have combined two responsibilities. (creating and calling or to phrase it differently: deciding who should do something and letting it do it). The remedy to this is to create the B instance outside of A and put it into A. Depending on the use case you have different options <ul> <li>create a B outside of A and stuff it into A through the constructor. This is the correct way to go if A needs the B in multiple places and it needs exactly one.</li> <li>create a B outside of A and stuff it into A through some method call. This is the correct way if A needs the B(s) for a single interaction and needs/accept a different one on the next interaction.</li> <li>pass a factory into A which A can use to create Bs at will. This is appropriate when A needs multiple Bs.</li> </ul> So this leaves the question: why is it so bad to use the constructor directly, instead of the factory, apart of violating some weired rule put up by a really smart person? If A creates Bs by calling the constructor for B it needs to know everything B needs for doing its work, which might be a lot of stuff and involve the necessety to create Cs, Ds and Es which themselves have dependencies which need to get created ... I think you see the point.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODoubts regarding the use of factory function in java
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJens Schauder
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.