.NET Brain Droppings

I'm a Microsoft Certified Architect (MCA)... Feel free to ask me about the program...

Cross Post: Yukon - How do you report from tables that use User Defined Types

I'm cross-posting this... I sent it to the Yukon newsgroups but I don't seem to be getting any bites.  Anyone out there have any advice about this.  Thanks!

Maybe someone out there can help me answer this question.

We're thinking about punting on pursuing an Object/Relational mapping tool
and instead allow developers that use Yukon to persist .NET objects via User
Defined Types.

There is one unknown though; how would a reporting tool report against a
table that now has a mix of relational data and object data in it?
Furthermore, would the report generator need to have a reference to the
assembly into order to query the table?

I've googled the heck out of this topic with no luck, so hopefully someone
on this list has attempted to report against tables with UDT's.  If you
have, can you relay your experience?

Posted: Aug 26 2004, 02:53 PM by dbrowning | with 1 comment(s)

Comments

Dave Sussman said:

Clients accessing UDT columns certainly need a reference to the assembly containing the UDT, but only if they access the type itself. For example, "SELECT * ..." would fail since the underlying type would be returned. With a reference the client wouldn't know the type of the UDT column. Directly calling methods on the type does work though, as these are called server side. So "SELECT MyUDTCol.ToString() ..." would work. You can put the assembly in the GAC to get the "SELECT * ..." scenario to work.
# August 26, 2004 4:42 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)