FOR XML issue

[guest2013-1]

I have the following

declare @perc float

set @perc = 75

select @perc

select @perc FOR XML RAW, TYPE, ELEMENTS

If you execute it you get:

75

<row>7.500000000000000e+001</row>

WTF on the <row>

Why is it doing that? How can I correct it? I need to use float values in my select statements that will go into XML format like that. But I can't afford the data being different when you output it as XML...

The money type field works perfectly, but I don't want to "money" all my floats.... just not right...

 

[dequadin]

Have you tried casting?

SELECT CONVERT(varchar(100), CAST(@perc AS decimal(38,2)))

Found that here

 

[guest2013-1]

I don't convert it to varchar, I did see those result but I figured "no, I'm using FOR XML and it's outputting XML, not trying to convert it".

Why decimal though? What happens to fields that's float? Would you say that as a standard I need to start implementing decimal instead of float?

 

[Shred]

Floats can be funny things. I would just use decimal from the start.

 

[guest2013-1]

Ok, new rule for me. Anything that needs .0000 = decimal

Thanks guys...

 

[FarligOpptreden]

I always, always, ALWAYS use decimal. Can't remember the last time I used float...

EDIT: Just a question though, why use FOR XML "RAW" and not "AUTO" or "EXPLICIT"? You have a lot more control over the element / attribute output in EXPLICIT and AUTO output modes...

 

[guest2013-1]

I always, always, ALWAYS use decimal. Can't remember the last time I used float...

EDIT: Just a question though, why use FOR XML "RAW" and not "AUTO" or "EXPLICIT"? You have a lot more control over the element / attribute output in EXPLICIT and AUTO output modes...

I use it so that I can parse it easier in my one stored procedure that converts the XML to json format. I want something simple and quick, and don't need to mess around too much with the data. So if a table can be quickly outputted to <row><your>Mother</your></row> by just a simple select. I'm happy.