Home Dashboard Directory Help
Search

Entity Designer mishandles View inclusion re Key and Read-only by SAinCA


Status: 

Closed
 as By Design Help for as By Design


1
0
Sign in
to vote
Type: Bug
ID: 699163
Opened: 11/4/2011 1:27:09 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

LightSwitch is UNUSABLE with a SQL Server 2005 Enterprise Edition View that has an INSTEAD OF trigger to handle all INSERT/UPDATE/DELETE activity.

It attempts to apply "intelligence" to defining a key for the View, whether or not the View has a Unique Index. It takes _ALL_ mandatory fields from contributing tables and makes them ALL (SEVENTEEN OF THEM IN MY CASE!) the Key of the View - preposterous!

It then states it has made the View read-only! Crass decision when there exists an INSTEAD OF trigger as mentioned above.

There is NO mechanism for "correcting" the inappropriate actions set in concrete by the Designer.

This is clearly a design flaw that renders the very promising development tool completely unusable with schema that employ this perfectly normal and admissible table-view-trigger architecture.
Details
Sign in to post a comment.
Posted by Microsoft on 11/8/2011 at 10:50 AM
Hi,

Your issues are a result of known limitations in the current release. We are logging these issues for possible inclusion in a future release.

Best regards,
Dan Leeaphon
VS LightSwitch
Sign in to post a workaround.