StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11939267
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-08-13T17:27:04.440
FavoriteCount
0
LastActivityDate
2012-08-13T17:36:11.007
LastEditDate
2012-08-13T17:36:11.007
LastEditorUserId
144302
OwnerUserId
144302
ParentId
11939025
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Recall that the Factory Pattern is used to create object without specifying the exact class of the object, thus decreasing the coupling between those two components. The Abstract Factory Pattern even decreases the amount of de-coupling by defining an interface which all factories must implement. Thus the caller of the abstract factory doesn't know anything about the implementation of factory and how objects are created. The caller just nows, calling a method on the factory will yield a certain object instance of interface X. The XML Library example from Matt is actually a good example. The abstract factory is the entity creating the XML parser which creates a <code>Document</code> object representing the actual document you parse. Actually, for you as a caller, it is most of the time completely irrelevant which Parser is used, as long as you get a <code>Document</code> object out of it. Therefore you can simply use the abstract factory. Which creates you a valid parser (most of the times ;)) The Toolkit example (also mentioned by Matt) is a more school-book like example. Imagine you just want to populate a window on the user screen. As you want to do it in a platform independent way, you define an abstract class Window with which you can do certain operations. Then you create an object which creates these windows, let's say <code>Win32WindowsFactory</code>. However, as your code shall be platform-independet, you define an interface <code>WindowsFactory</code> which provides you a method <code>createWindow()</code>. When the <code>Win32WindowsFactory</code> is used, a <code>Win32Window</code> is returned, when a <code>LinuxGTKWindowsFactory</code> is used, a <code>GTKWindow</code> is returned. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORegarding undrestanding of abstract factory pattern
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USStephan
UserOwnerUserId
1. USStephan
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. COSome confusion here. I would say the DocumentBuilderFactory is actually the abstract factory and the DocumentBuilder is the abstract product of that factory.
 singulars
 PostPostId
 PO
 UserUserId
 USlost
2. COYou are right, I edited it to reflect it.
 singulars
 PostPostId
 PO
 UserUserId
 USStephan

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.