Re: Bug in SQLXML

From: Peter Stokes (anonymous_at_discussions.microsoft.com)
Date: 03/22/04 

Date: Sun, 21 Mar 2004 19:06:06 -0800

Yes I am using SP2
     
     ----- Irwin Dolobowsky[MS] wrote: -----
     
     Does it repro in SP2? If so I can file a bug.
     
     --
     Irwin Dolobowsky
     Program Manager - SqlXml
     http://weblogs.asp.net/irwando
     
     This posting is provided "AS IS" with no warranties, and confers no rights.
     "Chris" <a@abc.com> wrote in message
     news:#$YlKjbBEHA.2584@TK2MSFTNGP12.phx.gbl...
> Hi Peter,
>> I can confirm that bug within SqlXml 3.0Sp1 I think b1. A joined table
     with
> a bit column returns always 0 if the result of the query is rendered to
     XML
> with "FOR XML NESTED" clause.
>> Two ways to get around:
>> 1. Use the clause "FOR XML RAW" and render the output with a xslt
     style***
> 2. Use a cast statment for the bit colomn and render it to a string, e.g.
> CAST(MyTable.Active AS NVARCHAR(1)) AS Active
>> Hope that helps.
>> Christian
>> "Peter Stokes" <anonymous@discussions.microsoft.com> wrote in message
> news:D71A19B0-5431-4A9F-9B6A-82500725E4DC@microsoft.com...
>> All,
>>>> I have a stored procedure which joins three nested tables. When I use
     the
> SQLXML managed classes for .NET to return this stored procedure as an
> xmlreader something strange happens.
>>>> In the top level table there is a boolean column. In the database the
> value of this column in the rows being returned is 1. However in the xml
> being returned the element has a value of 0. When I change the stored
> procedure and only return rows from the top level table it returns the xml
> correctly
>>>> Has anyone else experienced this?
>>>>