StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20488332
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-10T07:15:56.963
FavoriteCount
0
LastActivityDate
2013-12-10T07:15:56.963
LastEditDate
LastEditorUserId
0
OwnerUserId
1078381
ParentId
20487998
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
Here is a quote from the Josh Suereth <a href="http://www.manning.com/suereth2/">book</a> <blockquote> Defining Dependencies sbt provides a convenient syntax for defining Maven/Ivy dependencies using the % method. To define a ModuleID in sbt, just write “groupId” % “artifactId” % “version” and it will automatically become an instance of a ModuleID. </blockquote> Consider this dependency: <pre><code>libraryDependencies += "iv.alex" % "commons" % "100500" </code></pre> In this line we have three parts: <pre><code>libraryDependencies - setting key += - operator "iv.alex" % "commons" % "100500" - initialization part </code></pre> This initialization part constructs a <code>ModuleID</code>, which is required by <code>libraryDependencies</code> setting key. It consists from other three parts from the quote: <pre><code>"iv.alex" - groupId "commons" - artifactId "100500" - version </code></pre> But <code>libraryDependencies</code> key is actually a <code>Seq[ModuleID]</code>, so you have the second operator <code>++=</code> which expects a sequence of moduleIds: <pre><code>libraryDependencies ++= Seq("group" % "artifact" % "version", etc...) </code></pre> The most common way is to store dependencies in stores like <a href="http://search.maven.org/">maven cetnral</a>. So if you want to add you own dependency, for example you want to find <code>Akka</code> 2.2.3 for scala 2.11, first find it (<a href="http://search.maven.org/#browse%7C411317036">link</a>), then you need to find <code>.pom</code> file or some cases it would be written like <a href="http://mvnrepository.com/artifact/com.typesafe.akka/akka-actor_2.10/2.3-M1">here</a>, so you need the foloowing lines: <pre><code><dependency> <groupId>com.typesafe.akka</groupId> <artifactId>akka-actor_2.10</artifactId> <version>2.3-M1</version> </dependency> </code></pre> It is easy to translate into sbt dependency, like i've described above: <pre><code>libraryDependencies += "com.typesafe.akka" %% "akka-actor" % "2.3-M1" </code></pre> Note! that i've written <code>"com.typesafe.akka" %% "akka-actor"</code> two percentage symbols, it means that i need a library with the same version of scala which i have in my <code>scalaVersion</code> setting key. If you notice in maven style dependency, artifact id contains scala version: <code>akka-actor_2.10</code>, but not in out sbt dependency. If you don't have scala version in you artifactId, then you <code>shouldn't</code> write it as <code>%%</code> leave just one <code>%</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POsbt build file dependency syntax(or pattern)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. US4lex1v
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POsbt build file dependency syntax(or pattern)
 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.