StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20296362
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-30T04:05:14.343
FavoriteCount
0
LastActivityDate
2013-12-02T20:41:18.640
LastEditDate
2013-12-02T20:41:18.640
LastEditorUserId
2608009
OwnerUserId
2608009
ParentId
20111136
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You want to use <code>for</code> in a nested fashion: <pre><code>(for [i (range 1 (inc 4))] (for [j (range 1 (inc 3))] (+ (* 10 i) j))) ;; '((11 12 13) (21 22 23) (31 32 33) (41 42 43)) </code></pre> EDIT: expanded with an example implementation For example: <pre><code>(defn build-seq [f lower upper step] (for [i (range lower (+ upper step) step)] (f i))) (build-seq #(* % %) 2 6 2) ;; '(4 16 36) (defn build-table [f [ilower iupper] [jlower jupper]] (for [i (range ilower (inc iupper))] (for [j (range jlower (inc jupper))] (f i j)))) (build-table #(+ (* 10 %) %2) [1 4] [1 3]) ;; '((11 12 13) (21 22 23) (31 32 33) (41 42 43)) </code></pre> Your three input/output samples do not display a consistent signature for one variable and two ; furthermore, the <code>step</code> argument seems to be optional. I'm skeptical about the existence of a nice API that would retain the samples' syntax, but I can try something different (even if I do believe the simple embedded <code>for</code> forms are a better solution): <pre><code>(defn flexible-range [{:keys [lower upper step] :or {lower 0}}] (let [[upper step] (cond (and upper step) [(+ upper step) step] step (if (pos? step) [Double/POSITIVE_INFINITY step] [Double/NEGATIVE-INFINITY step]) upper (if (< lower upper) [(inc upper) 1] [(dec upper) -1]) :else [Double/POSITIVE_INFINITY 1])] (range lower upper step))) (defn build-table ([f [& params]] (for [i (flexible-range params)] (f i))) ([f [& iparams] [& jparams]] (for [i (flexible-range iparams)] (for [j (flexible-range jparams)] (f i j))))) (build-table #(* % %) [:lower 2 :upper 6 :step 2]) ;; '(4 16 36) (build-table #(+ (* 10 %) %2) [:lower 1 :upper 4] [:lower 1 :upper 3]) ;; '((11 12 13) (21 22 23) (31 32 33) (41 42 43)) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBuilding tables in clojure
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USomiel
UserOwnerUserId
1. USomiel
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBuilding tables in clojure
 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
 VTAcceptedByOriginator
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.