StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18955790
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-23T09:25:08.787
FavoriteCount
0
LastActivityDate
2013-09-23T13:23:21.640
LastEditDate
2013-09-23T13:23:21.640
LastEditorUserId
665679
OwnerUserId
665679
ParentId
18828067
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<p>So now I've tried to use Scalaz Either (which is a right biased Either compared to the neutral scala Either) and the Monad Transformer EitherT and it seems it does exactly what I want. Thanks to Huw and especially Lars Hupel for hinting me in the right direction.</p> <p>Here is working a sample for Twitter futures and Scalaz Either and EitherT:</p> <pre><code>import com.twitter.util.{Await, Future} import scalaz.{Monad, Functor, EitherT, \/} import scalaz.syntax.ToIdOps object EitherTest extends App with ToIdOps{ // make Twitter futures work with EitherT implicit val FutureFunctor = new Functor[Future] { def map[A, B](a: Future[A])(f: A => B): Future[B] = a map f } implicit val FutureMonad = new Monad[Future] { def point[A](a: => A): Future[A] = Future(a) def bind[A, B](fa: Future[A])(f: (A) => Future[B]): Future[B] = fa flatMap f } // The example begins here: case class InvalidInfo(error: String) case class Response(msg: String) class ComponentA { def foo(fail: Boolean): Future[\/[InvalidInfo, Response]] = { if(fail) Future(InvalidInfo("Error A").left) else Future(Response("ComponentA Success").right) } } class ComponentB { def bar(fail: Boolean): Future[\/[InvalidInfo, Response]] = { if(fail) Future(InvalidInfo("Error B").left) else Future(Response("ComponentB Success").right) } } val a = new ComponentA val b = new ComponentB val result = for { resultA <- EitherT(a.foo(false)) resultB <- EitherT(b.bar(false)) } yield (resultA, resultB) println(Await.result(result.run)) } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCombining Futures (Twitter) and Either in Scala
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USlongliveenduro
UserOwnerUserId
1. USlongliveenduro
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCombining Futures (Twitter) and Either in Scala
  singulars
  PostTypePostTypeId
  PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
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.