Datatype conversion Error

Question

0.00/5 (No votes)

See more:

Oracle Column Data Type NUMBER(28,2) is giving error when trying to convert it into linq,

C#

let _number=p.Field<double>("Number")

error is Specified cast is not valid.

Posted 22-Jun-14 3:01am

shaprpuff

Updated 22-Jun-14 3:02am

v2

Add a Solution

Comments

CHill60 22-Jun-14 9:17am

Could this be because you've used a reserved word ("Number") as a column name?

ashok rathod 23-Jun-14 0:54am

you can check and verify that first to convert your respective string to string and then cast it to specific type double

V. 23-Jun-14 7:38am

Avoid having "keywords" as column names as it can give you problems.
Secondly were is it going wrong? Can you step into the code until this line, hightlight "p.Field<double>("Number")", right-click and choose quickwatch. it will give you the value and the type normally. Decimal should convert to double without issues normally. Not sure how the let keyword reacts to this, can you remove it just to test?
[EDIT]It can very well be that decimal does not convert to double implicitly, so better check that indeed.[/EDIT]

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

johannesnestler · Accepted Answer · 2014-06-23T01:19:00

Solution 1

Use decimal instead of double

Posted 23-Jun-14 1:19am

johannesnestler

Comments

Bernhard Hiller 24-Jun-14 3:12am

Also Oracle's "Number" definition is not fully compatible with .Net's "decimal": it could be necessary to use the "truncate" function in the SQL query to cut the number down to a number which can be represented by a "decimal".