You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stored procedure mapping (#28553) currently requires that a table mapping be defined; the table mapping is necessary in order for us to properly perform topological sort (e.g. know about dependencies between tables). It makes sense for users to use views/functions for querying and only sprocs for updating, in which case a table mapping isn't strictly speaking necessary.
In the meantime, can the exception message be updated to reflect that non-tables are not supported? It still says "An entity type that isn't mapped to a table must be mapped to insert, update and delete stored procedures." but the code doesn't allow any SP mapping to non-tables.
<value>The entity type '{entityType}' was configured to use some stored procedures and is not mapped to any table. An entity type that isn't mapped to a table must be mapped to insert, update and delete stored procedures.</value>
Stored procedure mapping (#28553) currently requires that a table mapping be defined; the table mapping is necessary in order for us to properly perform topological sort (e.g. know about dependencies between tables). It makes sense for users to use views/functions for querying and only sprocs for updating, in which case a table mapping isn't strictly speaking necessary.
See conversation in #28553 (comment)
The text was updated successfully, but these errors were encountered: