StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11806923
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-04T07:54:41.897
FavoriteCount
0
LastActivityDate
2012-08-04T07:54:41.897
LastEditDate
LastEditorUserId
0
OwnerUserId
0
ParentId
11802609
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Well, this might be possible, but depends on how much effort you are willing to put into writing eLisp code to make it work. It's not possible by just some configuration option. I would be looking into extending autocomplete by adding new sources to it, something like: <pre><code>(defvar tex-tag-ac-sources '((init . tex-tag-ac-init) (requires . 0) (candidates . tex-tag-ac-candidates) (document . tex-tag-ac-documentation) (match . tex-tag-completion-filter) (prefix . tex-tag-ac-prefix-matcher) (symbol . "s")) "The source generator for autocompletion needed for interaction with auto-complete") </code></pre> Where <code>tex-tag-ac-candidates</code>, <code>tex-tag-ac-documentation</code>, <code>tex-tag-completion-filter</code> and <code>tex-tag-ac-prefix-matcher</code> are function that do autocompletion. I.e. init function is called once when the autocompletion process starts for a specified prefix. It's called w/o arguments. The candidates is the function that is responsible for showing the filtered list of candidates, it's called w/o arguments, you would filter the candidates in the filter function, it is called with the prefix collected so far and the list of candidates so far. Lastly, the matcher function is invoked on the text of the file to see if the completion is needed at point. So, if it returns <code>t</code>, the init is called, and then loops through filter-candidates as you type. While this is a bit involved... you'd definitely have a completion for anything you want. Obviously, if those functions in source are defined by you, then, if you wanted to, you could read completion arguments dynamically or have them generated dynamically in some way. Ah, you would add the sources to autocomplete by something like: <pre><code>(auto-complete (list tex-tag-ac-sources)) </code></pre> if doing it on per call basis, or <pre><code>(setq ac-sources (list tex-tag-ac-sources <other sources>)) </code></pre> You can find more info here: <a href="http://cx4a.org/software/auto-complete/manual.html#Using_Source" rel="nofollow">http://cx4a.org/software/auto-complete/manual.html#Using_Source</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLisp: creating a macro to cycle through a created list per document
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. This table or related slice is empty.
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
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.