StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19610571
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-26T18:50:31.363
FavoriteCount
0
LastActivityDate
2018-06-29T19:51:22.690
LastEditDate
2018-06-29T19:51:22.690
LastEditorUserId
728790
OwnerUserId
728790
ParentId
19610320
PostTypeId
2
Score
44
ViewCount
0
LastEditorDisplayName
text
Body
You are using an immutable list. The operations on the List return a new List. The old List remains unchanged. This can be very useful if another class / method holds a reference to the original collection and is relying on it remaining unchanged. You can either use different named vals as in <pre><code>val myList1 = 1.0 :: 5.5 :: Nil val myList2 = 2.2 :: 3.7 :: mylist1 </code></pre> or use a var as in <pre><code>var myList = 1.0 :: 5.5 :: Nil myList :::= List(2.2, 3.7) </code></pre> This is equivalent syntax for: <pre><code>myList = myList.:::(List(2.2, 3.7)) </code></pre> Or you could use one of the mutable collections such as <pre><code>val myList = scala.collection.mutable.MutableList(1.0, 5.5) myList.++=(List(2.2, 3.7)) </code></pre> Not to be confused with the following that does not modify the original mutable List, but returns a new value: <pre><code>myList.++:(List(2.2, 3.7)) </code></pre> However you should only use mutable collections in performance critical code. Immutable collections are much easier to reason about and use. One big advantage is that immutable List and <a href="http://www.scala-lang.org/api/current/#scala.collection.immutable.Vector" rel="nofollow noreferrer">scala.collection.immutable.Vector</a> are Covariant. Don't worry if that doesn't mean anything to you yet. The advantage of it is you can use it without fully understanding it. Hence the collection you were using by default is actually <a href="http://www.scala-lang.org/api/current/#scala.collection.immutable.List" rel="nofollow noreferrer">scala.collection.immutable.List</a> its just imported for you automatically. I tend to use List as my default collection. From 2.12.6 Seq defaults to immutable Seq prior to this it defaulted to immutable.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAdd element to a list In Scala
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRich Oliver
UserOwnerUserId
1. USRich Oliver
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAdd element to a list 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
 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.