StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POCreating different POCO's from a single type
primarykey
Id
4601238
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-01-05T06:00:30.777
FavoriteCount
0
LastActivityDate
2011-01-07T08:57:38.887
LastEditDate
LastEditorUserId
0
OwnerUserId
120243
ParentId
0
PostTypeId
1
Score
2
ViewCount
119
LastEditorDisplayName
text
Body
I'm writing a wrapping library around a <a href="http://en.wikipedia.org/wiki/SCADA" rel="nofollow">SCADA</a> database and I've got a small 'hippy-code-design' question. It involves how I'm converting the supplied DB objects into POCO's. I'm calling the DB using the vendors .NET libraries. When I make calls the DB, it passes back an object of type <code>DBObject</code>. This can represent anything in the database, and as such is quite generic in the information that it holds. Any custom information is accessed from the DB with a <code>DBObject.GetProperty()</code> method call, which requires the connection to the DB to be active. I'm looking to convert this basic <code>DBObject</code> into a variety of different POCO's so that I can pass them around via WCF and other tech. Currently I have a abstract base class called <code>ScadaObject</code> that has a number of base properties that I want all the POCO's to contain and a protected virtual method called <code>InternalFromDBObject(DBObject obj)</code> which performs this creating from the <code>DBObject</code> into the POCO. In my derived types I override this method, call <code>base.InternalFromDBObject(obj)</code> as the first call, then proceed to load any custom/specific information. I then have a static method on the POCO called <code>FromDBObject()</code> which returns a new instance of that POCO. Is this a good way to do things? I'm not hugely experienced in using factories so I'm not sure if they would fit. Is there any other design patterns I could use?
Tags
<.net><design-patterns><poco>
Title
Creating different POCO's from a single type
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USAlastair Pitts
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POCreating different POCO's from a single type
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POCreating different POCO's from a single type
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COSeems just as painful as most approaches I have seen :(
 singulars
 PostPostId
 POCreating different POCO's from a single type
 UserUserId
 USleppie

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.