StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4279645
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
2010-11-25T17:39:16.537
CreationDate
2010-11-25T17:39:16.537
FavoriteCount
0
LastActivityDate
2010-11-25T17:39:16.537
LastEditDate
LastEditorUserId
0
OwnerUserId
16853
ParentId
4277008
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
Not that I'm banging the same drum again but... A solution for the problem where we have a number of processes which may produce a successful output, or fail with some error message. The goal is to aggregate the successful outcomes, if all processes produce a success and if one or more fails, to aggregate all error messages. This can be solved by scalaz validation: firstly, setup some imports <pre><code>scala> import scalaz._; import Scalaz._ import scalaz._ import Scalaz._ </code></pre> Now let's define our "processes" <pre><code>scala> def fooI(s : String) : ValidationNEL[Exception, Int] = s.parseInt.liftFailNel fooI: (s: String)scalaz.Scalaz.ValidationNEL[Exception,Int] scala> def fooF(s : String) : ValidationNEL[Exception, Float] = s.parseFloat.liftFailNel fooF: (s: String)scalaz.Scalaz.ValidationNEL[Exception,Float] scala> def fooB(s : String) : ValidationNEL[Exception, Boolean] = s.parseBoolean.liftFailNel fooB: (s: String)scalaz.Scalaz.ValidationNEL[Exception,Boolean] </code></pre> Now use <code>Applicative</code> to aggregate the failures/successes: <pre><code>scala> def attempt(ss : String*) = (fooI(ss(0)) <|**|> (fooF(ss(1)), fooB(ss(2)))) match { | case Success((i, f, b)) => println("Found " + i + " " + f + " " + b) | case Failure(es) => es foreach println | } attempt: (ss: String*)Unit </code></pre> Now let's try for some failures: <pre><code>scala> attempt("a", "b", "true") java.lang.NumberFormatException: For input string: "a" java.lang.NumberFormatException: For input string: "b" </code></pre> Now let's try for success: <pre><code>scala> attempt("1", "2.3", "false") Found 1 2.3 false </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat common patterns/solutions have been established in Scala for frequently-encountered problems
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USoxbow_lakes
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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.