{"action":"opened","issue":{"url":"https://api.github.com/repos/npgsql/EntityFramework6.Npgsql/issues/49","repository_url":"https://api.github.com/repos/npgsql/EntityFramework6.Npgsql","labels_url":"https://api.github.com/repos/npgsql/EntityFramework6.Npgsql/issues/49/labels{/name}","comments_url":"https://api.github.com/repos/npgsql/EntityFramework6.Npgsql/issues/49/comments","events_url":"https://api.github.com/repos/npgsql/EntityFramework6.Npgsql/issues/49/events","html_url":"https://github.com/npgsql/EntityFramework6.Npgsql/issues/49","id":176877742,"number":49,"title":"Code frist migrations fail to create multi column indexes","user":{"login":"cakkermans","id":8382279,"avatar_url":"https://avatars.githubusercontent.com/u/8382279?v=3","gravatar_id":"","url":"https://api.github.com/users/cakkermans","html_url":"https://github.com/cakkermans","followers_url":"https://api.github.com/users/cakkermans/followers","following_url":"https://api.github.com/users/cakkermans/following{/other_user}","gists_url":"https://api.github.com/users/cakkermans/gists{/gist_id}","starred_url":"https://api.github.com/users/cakkermans/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cakkermans/subscriptions","organizations_url":"https://api.github.com/users/cakkermans/orgs","repos_url":"https://api.github.com/users/cakkermans/repos","events_url":"https://api.github.com/users/cakkermans/events{/privacy}","received_events_url":"https://api.github.com/users/cakkermans/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-14T11:02:00Z","updated_at":"2016-09-14T11:02:00Z","closed_at":null,"body":"According to MSDN it is possible to specify multi column (unique) indexes using attributes. Hence I would expect them to be created accordingly during a migration. Unfortunately only the first column is added to the index :/\r\n\r\nhttps://msdn.microsoft.com/en-us/data/jj591583.aspx#IndexMulti\r\n\r\nI checked the Migration SQL generator implementation of Npgsql and it looks fine. For some reason it seems like the entity framework is not passing on the complete set of columns, resulting in Npgsql also simple not adding them all to the index to be created. The result is an index being created only on the first column.\r\n\r\nAm I missing something?\r\n\r\nI created a pull request which expands on the migration unit tests to demonstrate the problem: npgsql/EntityFramework6.Npgsql#46\r\n"}}
{"actor":{"display_login":"cakkermans"}}