ajcvickers

user stats

Member SinceNovember 14, 2011
Last VisitSeptember 17, 2014

Contact

developer for

Entity Framework

ajcvickers

personal statement

Developer at Microsoft working on the Entity Framework.
Twitter: @ajcvickers
Blog: http://blog.oneunicorn.com/

activity stream

September 16, 2014 - Entity Framework: Created work item: Remove the EF5 sample provider from CodePlex

September 15, 2014 - Entity Framework: Modified work item: Explicit Composite Index Only Inludes One of Two Specified Columns

September 15, 2014 - Entity Framework: Commented work item: Explicit Composite Index Only Inludes One of Two Specified Columns

September 11, 2014 - Entity Framework: Modified work item: getting "entity types cannot share table" for same-named tables in different schemas

September 11, 2014 - Entity Framework: Commented work item: getting "entity types cannot share table" for same-named tables in different schemas

September 9, 2014 - Entity Framework: Modified work item: Explicit Composite Index Only Inludes One of Two Specified Columns

September 9, 2014 - Entity Framework: Commented work item: Explicit Composite Index Only Inludes One of Two Specified Columns

September 9, 2014 - Entity Framework: Pushed d47b05aff4a16947169a494e17928b497a5bdf64, Cosmo and Dibs... (Fix for 2382: Explicit Composite Index Only Includes One of Two Specified Columns) The issue here was the foreign key index convention which was replacing any existing index on the column with the convention index. This didn't usually happen because if an explicit index is defined for the FK columns then the convention doesn't kick in. In this case the explicit index only spanned one column of the composite foreign key and so the convention still kicked in and the existing annotation on the column was clobbered.

September 9, 2014 - Entity Framework: Committed d47b05aff4a16947169a494e17928b497a5bdf64, Cosmo and Dibs... (Fix for 2382: Explicit Composite Index Only Includes One of Two Specified Columns) The issue here was the foreign key index convention which was replacing any existing index on the column with the convention index. This didn't usually happen because if an explicit index is defined for the FK columns then the convention doesn't kick in. In this case the explicit index only spanned one column of the composite foreign key and so the convention still kicked in and the existing annotation on the column was clobbered.

September 9, 2014 - Entity Framework: Committed d47b05aff4a16947169a494e17928b497a5bdf64, Cosmo and Dibs... (Fix for 2382: Explicit Composite Index Only Includes One of Two Specified Columns) The issue here was the foreign key index convention which was replacing any existing index on the column with the convention index. This didn't usually happen because if an explicit index is defined for the FK columns then the convention doesn't kick in. In this case the explicit index only spanned one column of the composite foreign key and so the convention still kicked in and the existing annotation on the column was clobbered.

projects i'm following

forks

No forks.