StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1311224
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-08-21T10:41:29.233
FavoriteCount
0
LastActivityDate
2009-08-21T10:41:29.233
LastEditDate
LastEditorUserId
0
OwnerUserId
77671
ParentId
1308765
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<a href="http://groups.google.com/group/sqlalchemy/browse_thread/thread/187b3c13fa49a069" rel="nofollow noreferrer">I asked this question on a mailing list and got this answer by Michael Bayer</a>: <blockquote> if you'd like distinct classes to indicate that they "belong" in a different database, and you have very clear lines as to how this is performed, use the "entity_name" concept described at <a href="http://www.sqlalchemy.org/trac/wiki/UsageRecipes/EntityName" rel="nofollow noreferrer">http://www.sqlalchemy.org/trac/wiki/UsageRecipes/EntityName</a> . this sounds very much like your use case. <blockquote> The next idea is to use sharding. For that we need a way to distinguish between the databases from the perspective of an instance, as noted in the docs: "You need a function which can return a single shard id, given an instance to be saved; this is called "shard_chooser" </blockquote> horizontal sharding is a method of storing many homogeneous instances across multiple databases, with the implication that you're creating one big "virtual" database among partitions - the main concept is that an individual instance gets placed in different partitions based on some ruleset. This is a little like your use case as well but since you have a very simple delineation i think the "entity name" approach is easier. </blockquote> So the basic idea is to generate anonymous subclasses for each desired mapping which are distinguished by the Entity_Name. The details can be found in <a href="http://www.sqlalchemy.org/trac/wiki/UsageRecipes/EntityName" rel="nofollow noreferrer">Michaels Link </a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMultiple Mappers for the same class in different databases
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPonk
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMultiple Mappers for the same class in different databases
 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.