StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16657607
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-20T20:14:51.443
FavoriteCount
0
LastActivityDate
2013-05-20T20:14:51.443
LastEditDate
LastEditorUserId
0
OwnerUserId
1535647
ParentId
16656312
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
It's hard to say without seeing some code, but you may want to look into implementing a Repository Pattern. The Repository implementation would be responsible for retrieving the data that the factory then used to build its object(s). You could inject the repository interface into your factory: <pre><code>public class ModelParameterFactory : IModelParameterFactory { private readonly IModelParameterRepository Repository; public ModelParameterFactory(IModelParameterRepository repository) { Repository = repository; } ...interface methods use the injected repository... } </code></pre> Then you would have, say a DatabaseModelParameterRepository and a FileModelParameterRepository. But I'm guessing you also have logic around which of those you would need to inject, so that calls for another factory: <pre><code>public class ModelParameterRepositoryFactory : IModelParameterRepositoryFactory { public ModelParameterRepositoryFactory(...inputs needed to determine which repository to use...) { ...assign... } ...determine which repository is required and return it... } </code></pre> At this point, it might make more sense to inject IModelParameterRepositoryFactory into the ModelParameterFactory, rather than inject the IModelParameterRepository. <pre><code>public class ModelParameterFactory : IModelParameterFactory { private readonly IModelParameterRepositoryFactory RepositoryFactory; public ModelParameterFactory(IModelParameterRepositoryFactory repositoryFactory) { RepositoryFactory = repositoryFactory; } ...interface methods get repository from the factory... } </code></pre> Whether you use a DI container or not, all logic regarding which repository to use and which factory to use are now moved into the relevant factory implementations, as opposed to the calling code or DI configuration. While not terribly complex, this design nonetheless does give me pause to wonder whether your ModelParameterFactory and ModelParameters are too generic. You might benefit from teasing them into separate, more specific classes. The result would be a simpler and more expressive design. The above should work for you if that is not the case, however.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODealing with state in factory implementations
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFacio Ratio
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.