StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19617079
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-27T10:32:51.500
FavoriteCount
0
LastActivityDate
2013-10-27T10:32:51.500
LastEditDate
LastEditorUserId
0
OwnerUserId
614482
ParentId
14731979
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I don't know of any way to achieve this without custom code which would manipulate the active profiles in a <code>ConfigurableEnvironment</code>. We're trying to achieve the same indirection pattern as rights vs. roles (group of rights) in a security framework, but since this doesn't come out of the box, I ended up having to work around it. I kept my profiles general, e.g. production and super-fast in your case, and for each bean that is sensitive to those profiles, I set the correct @Profile. To make refactoring easier, I used two techniques. <ol> <li>Create a meta-annotation for each profile, e.g. <code>@Production</code>, <code>@SuperFast</code> and make the profile name a public constant, e.g. <code>Production.PROFILE_NAME = "production"</code>.</li> <li>When marking the profile of any bean, use your new meta-annotation if it only applies to one profile, or use <code>@Profile({Production.PROFILE_NAME, ...})</code> if it applies to multiple profiles. You have to do this because you can't apply two profile meta-annotations to the same bean, <a href="https://jira.springsource.org/browse/SPR-10812" rel="nofollow">at least not until 4.0</a>.</li> </ol> For example, <pre><code>@Profile(Production.PROFILE_NAME) public @interface Production { public static String PROFILE_NAME = "production"; } </code></pre> The point of all this is that you can now use your IDE to look for usages of <code>@Production</code> or <code>Production.PROFILE_NAME</code> if you need to quickly understand or change what beans are being pulled in. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POspring profile groups
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USEmerson Farrugia
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. This table or related slice is empty.
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.