StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8335778
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-12-01T02:14:34.457
FavoriteCount
0
LastActivityDate
2011-12-01T02:43:06.683
LastEditDate
2011-12-01T02:43:06.683
LastEditorUserId
409386
OwnerUserId
409386
ParentId
2305743
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Indices are not supported natively, but if you head to the "Influencing the DDL Generation" section of <a href="http://msdn.microsoft.com/en-us/data/ff830362.aspx" rel="nofollow">this</a> article you can see how to add this custom functionality to an existing template. In the article's example, the new index in your EDMX's CSDL would look something like this: <pre><code><Property ... > <myExtensions:Index indexName="Seat" edmx:CopyToSSDL="true"/> </Property> </code></pre> But to get this working you would have to modify a few things (see the link I provided for the details). Firstly, you'd have to declare that "myExtensions" namespace on the schema node: <pre><code> <edmx:ConceptualModels> <Schema [...] xmlns:myExtensions="http://www.microsoft.com/userExtensions"> [...] </edmx> </code></pre> Secondly, you'd have to modify the template found at: <blockquote> \Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft\Entity Framework Tools\DBGen\SSDLToSQL10.tt </blockquote> The solution requires Linq, so add this to the top of the template: <pre><code><#@ assembly name="System.Xml.Linq" #> </code></pre> And then add this to the bottom: <pre><code>-- Creating index for table based on custom extensions -- <# foreach (EntitySet entitySet in Store.GetAllEntitySets()) { string tableName = Id(entitySet.GetTableName()); string schemaName = Id(entitySet.GetSchemaName()); EdmProperties props = entitySet.ElementType.Properties; foreach (EdmProperty ep in props.Where(p => p.TypeUsage.EdmType is PrimitiveType)) { MetadataProperty meta = ep.MetadataProperties.FirstOrDefault(mp => mp.Name == "http://www.microsoft.com/userExtensions:Index"); if (meta != null) { System.Xml.Linq.XElement e = meta.Value as System.Xml.Linq.XElement; System.Xml.Linq.XAttribute attr = e.Attributes().FirstOrDefault(a => a.Name == "indexName"); string indexName = attr.Value; // create an index for specified column #> CREATE INDEX [IX_<#=indexName#>] ON <#if (!IsSQLCE) {#>[<#=schemaName#>].<#}#>[<#=tableName#>] ([<#=indexName#>]); <# } } } #> </code></pre> Most of that could be pretty easily modified to fit your needs. The article goes into more of the details, but the most important line in the above code is the one which fetches that custom "Index" extension node: <pre><code>MetadataProperty meta = ep.MetadataProperties.FirstOrDefault(mp => mp.Name == "http://www.microsoft.com/userExtensions:Index"); </code></pre> Hope that helps!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEntity Framework Code Generation with Indexes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSmudge
UserOwnerUserId
1. USSmudge
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
CommentsPostId
1. COvery nice answer, thanks
 singulars
 PostPostId
 PO
 UserUserId
 USFrancisco

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.