1

using c# mvc4 and mssql I have an Object which has a float field, now when I look it in the database the float value is 2.014112E+17 but when I get the object in my code, it becomes 2.01411186E+17. why is it different between the object in the server and the object in the database? there is no conversion happening in between by me, just reading an object from database. Thank you

Edit: I'm using this float point as a timestamp to sync some of my data with another database and this issue is causing is me some problems, is there a way to get an accurate value or storing it as a float is a wrong idea in first place?

Improve this question
4
  • 1
    Looks like just rounding or representation stuff? Commented Nov 18, 2014 at 13:44
  • Are you actually comparing the floats in code, or just their string representation? Commented Nov 18, 2014 at 13:44
  • @JarekPiórkowski yea I'm comparing the floats, there's no string representation of those, I get the object via linq, read the float value as float and compare it to another float value. Commented Nov 18, 2014 at 13:47
  • 3
    if you need accuracy, use Decimal, not float or double. Commented Nov 18, 2014 at 13:53

2 Answers 2

Reset to default
5

Floats are only accurate to a certain degree due to their implementation. For accuracy, use Decimal.

Difference between decimal, float and double in .NET?

float and double are floating binary point types. In other words, they represent a number like this:

10001.10010110011

The binary number and the location of the binary point are both encoded within the value.

decimal is a floating decimal point type. In other words, they represent a number like this:

12345.65789

Edit: You can also try saving the timestamp as a unix timestamp, which is just the number of seconds since 1970-01-01. It might be better suited for your needs

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

I'm getting the timestamp like decimal.Parse(DateTime.Now.ToString("yyyyMMddHHmmss"));. is there a chance that the value will be bigger than the decimal range?
@arashmoeen - the value being out of range would depend on how you define the decimal. Up to you to figure out what your needs are.
I'd rather to go with your unix timestamp solution which I wasn't aware of, I'll get the total seconds like "long unixTimestamp = (long)(DateTime.UtcNow.Subtract(new DateTime(1970, 1, 1))).TotalSeconds;" which should do the job for me as I wanted. can you please edit you answer including the unit timestamp solution so I can accept it as answer?
4

If you have literally used a SQL float with a C# float, these are not comparable. You should be using a SQL real to store your C# float.

See here for full chart: C# Equivalent of SQL Server DataTypes

As an aside, you will always have the potential for these issues when working with floating point numbers. Where possible, use a decimal instead.

Further reference for SQL float != C# float: Why is a SQL float different from a C# float

Improve this answer

2 Comments

or sql float with c# double
well I'm using code first in mvc4, so if I change my object's field from float to decimal, will it fix the problem ?

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.