StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17495444
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-07-05T19:08:55.897
FavoriteCount
0
LastActivityDate
2013-07-05T19:08:55.897
LastEditDate
LastEditorUserId
0
OwnerUserId
1333025
ParentId
16757060
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I don't know if it's any help, but I tried to implement Iain's suggestion and made a variant of <code>mergeSources'</code> that stops as soon as any of the channels does: <pre><code>mergeSources' :: (MonadIO m, MonadBaseControl IO m) => [Source (ResourceT m) a] -- ^ The sources to merge. -> Int -- ^ The bound of the intermediate channel. -> ResourceT m (Source (ResourceT m) a) mergeSources' sx bound = do c <- liftSTM $ newTBMChan bound mapM_ (\s -> resourceForkIO $ s $$ chanSink c writeTBMChan closeTBMChan) sx return $ sourceTBMChan c </code></pre> (This simple addition is available <a href="https://github.com/ppetr/stm-conduit/commits/master" rel="nofollow">here</a>). Some comments to your version of <code>mergeSources</code> (take them with a grain of salt, it can be I didn't understand something well): <ul> <li>Using <code>...TMChan</code> instead of <code>...TBMChan</code> seems dangerous. If the writers are faster than the reader, your heap will blow. Looking at your diagram it seems that this can easily happen, if your TCP peer doesn't read data fast enough. So I'd definitely use <code>...TBMChan</code> with perhaps large but limited bound.</li> <li>You don't need the <code>MonadSTM m</code> constraint. All STM stuff is wrapped into <code>IO</code> with <pre><code>liftSTM = liftIO . atomically </code></pre> Maybe this will help you slightly when using <code>mergeSources'</code> in <code>serverApp</code>.</li> <li>Just a cosmetic issue, I found <pre><code>liftSTM newTMChan >>= liftA2 (>>) (fsrc sx) retn </code></pre> very hard to read due to its use of <code>liftA2</code> on the <code>(->) r</code> monad. I'd say <pre><code>do c <- liftSTM newTMChan fsrc sx c retn c </code></pre> would be longer, but much easier to read.</li> </ul> Could you perhaps create a self-contained project where it would be possible to play with <code>serverApp</code>?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POOne processing conduit, 2 IO sources of the same type
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPetr Pudlák
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. COThanks for the advice. I'll keep it in mind (I'll have to revisit the problem soon).
 singulars
 PostPostId
 PO
 UserUserId
 USkvanberendonck

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.