Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>linq to sql relies heavily on attributes to map class (datacontext) members to database members. Your interfaces likely does not have the FunctionAttribute over the ufn_GRFO method. without that attribute the link between the C# world and the SQL function is severed; however. your interface is also not decorated with the DatabaseAttribute as that attribute is only valid on classes and not interfaces. without that attribute you have severed the link between C# and the whole database. by default Linq uses the AttributeMappingSource to map type members in the DataContext. Sense the interface is the type in question and that type has severed the link to that database, due to the fact that you can't apply the database attribute to it, your default mapping source will not map the function ufn_GRFO to the database function, rather linq will treat it as a .NET function to call with the data from the WFT field.</p> <p>I suspect the way around this issue is to provide your datacontext with a custom MappingSource implementation and that ignores the DatabaseAttribute and only considers the attributes on the properties.</p> <p><a href="http://msdn.microsoft.com/en-us/library/system.data.linq.mapping.functionattribute.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/system.data.linq.mapping.functionattribute.aspx</a></p> <p><a href="http://msdn.microsoft.com/en-us/library/system.data.linq.mapping.databaseattribute.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/system.data.linq.mapping.databaseattribute.aspx</a></p> <p><a href="http://msdn.microsoft.com/en-us/library/system.data.linq.mapping.attributemappingsource.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/system.data.linq.mapping.attributemappingsource.aspx</a></p> <p><a href="http://msdn.microsoft.com/en-us/library/system.data.linq.mapping.mappingsource.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/system.data.linq.mapping.mappingsource.aspx</a></p>
    singulars
    1. This table or related slice is empty.
    1. POLinqToSql DataContext with extracted interface doesn't compose SQL for functions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USjcwmoore
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POLinqToSql DataContext with extracted interface doesn't compose SQL for functions
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload