Wow... now that was some serious time off. I've had blog-vacations before; but never one that lasted over the span of months. Things got really busy at work, and I'm also working on a side project that is consuming all my "spare" cycles, so something had to give.
Let's see how long this lasts... I was on a good run prior to June so hopefully I can get back in the swing of things.
[Listening to: Jane's Addiction - Strays]
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
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?