{"action":"created","issue":{"url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3748","labels_url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3748/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3748/comments","events_url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3748/events","html_url":"https://github.com/aspnet/EntityFramework/issues/3748","id":116819542,"number":3748,"title":"Feature Request: Specifying Included Columns for an Index","user":{"login":"eriksendc","id":8974354,"avatar_url":"https://avatars.githubusercontent.com/u/8974354?v=3","gravatar_id":"","url":"https://api.github.com/users/eriksendc","html_url":"https://github.com/eriksendc","followers_url":"https://api.github.com/users/eriksendc/followers","following_url":"https://api.github.com/users/eriksendc/following{/other_user}","gists_url":"https://api.github.com/users/eriksendc/gists{/gist_id}","starred_url":"https://api.github.com/users/eriksendc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eriksendc/subscriptions","organizations_url":"https://api.github.com/users/eriksendc/orgs","repos_url":"https://api.github.com/users/eriksendc/repos","events_url":"https://api.github.com/users/eriksendc/events{/privacy}","received_events_url":"https://api.github.com/users/eriksendc/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-11-13T18:11:12Z","updated_at":"2015-11-18T15:21:11Z","closed_at":"2015-11-17T21:36:43Z","body":"Hi there,\r\n\r\nThanks again for the help with specifying an index using code first.\r\n\r\nOne thing that's commonly necessary in real world situations is a 'covering index', where you have the main columns that the RDBMS uses to search (seek), but then additional data is included in the index to prevent the RDBMS from having to go to the heap table to do an extra lookup. In SQL Server this list of columns goes after the INCLUDE keyword:\r\n\r\nCREATE INDEX IX_SomeObject_SomeDateTimeProperty ON dbo.SomeObject (SomeDateTimeProperty) INCLUDE (SomeStringProperty)\r\n\r\nI'm sure you know all this. You guys are gurus! :) Anyways, I understand that to target different RDBMS's you don't want to throw every feature of the RDBMS into EF, but I think that the concept of covering indexes is fairly mature and supported by all major RDBMS's in use today. \r\n\r\nPlease accept this as a long-term suggestion for EF7.\r\n\r\nThanks and regards,\r\n-Brian Eriksen\r\n\r\nPS - When someone gives this a read, if there's a good resource that calls out how you deal with DB objects that EF doesn't handle, it'd be great to be directed to that. I'm transitioning to code first from database first, and I'm also used to having a database project to manage all DDL. Thanks so much in advance!"},"comment":{"url":"https://api.github.com/repos/aspnet/EntityFramework/issues/comments/157746212","html_url":"https://github.com/aspnet/EntityFramework/issues/3748#issuecomment-157746212","issue_url":"https://api.github.com/repos/aspnet/EntityFramework/issues/3748","id":157746212,"user":{"login":"eriksendc","id":8974354,"avatar_url":"https://avatars.githubusercontent.com/u/8974354?v=3","gravatar_id":"","url":"https://api.github.com/users/eriksendc","html_url":"https://github.com/eriksendc","followers_url":"https://api.github.com/users/eriksendc/followers","following_url":"https://api.github.com/users/eriksendc/following{/other_user}","gists_url":"https://api.github.com/users/eriksendc/gists{/gist_id}","starred_url":"https://api.github.com/users/eriksendc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eriksendc/subscriptions","organizations_url":"https://api.github.com/users/eriksendc/orgs","repos_url":"https://api.github.com/users/eriksendc/repos","events_url":"https://api.github.com/users/eriksendc/events{/privacy}","received_events_url":"https://api.github.com/users/eriksendc/received_events","type":"User","site_admin":false},"created_at":"2015-11-18T15:21:11Z","updated_at":"2015-11-18T15:21:11Z","body":"Thanks for considering this and providing me with direction. \n\n-Brian \n\n> On Nov 17, 2015, at 4:37 PM, Rowan Miller <notifications@github.com> wrote:\n> \n> We discussed in triage and concluded that for the moment using Sql(...) to create the index is the right approach. If we see a significant number of folks wanting to be able to specify included columns in the model then we may reconsider adding it to the core model.\n> \n> —\n> Reply to this email directly or view it on GitHub.\n> \n"}}