Hibernate MS-SQL Wrong column type Found: decimal, expected: float

Question

Note: Answer at end of question

I have created some columns in my My SQL database and have evidently not created floating point before because I had to look it up. For SQL compliance, I created my columns thus:

ALTER TABLE sensor ADD Field1_Calibration_Offset DECIMAL(4, 3);

Times 8 for each column.

I have defined these in my java code such:

@Column(name = "FIELD1_CALIBRATION_OFFSET") private Float field1CalibrationOffset;

which generated the error:

Wrong column type in PsDb.dbo.Sensor for column FIELD1_CALIBRATION_OFFSET. Found: decimal, expected: float

Final Answer

Following @jbrookover's answer below, I changed to BigDecimal, I got:

Wrong column type in PsDb.dbo.Sensor for column FIELD1_CALIBRATION_OFFSET. Found: decimal, expected: numeric(19,2)

So I looked up my hibernate mappings and did:

@Column(name = "FIELD1_CALIBRATION_SCALE", columnDefinition="decimal", precision=4, scale=3)
private BigDecimal field1CalibrationScale;

jbrookover · Accepted Answer · 2011-10-10 12:29:49Z

12

I tend to let Hibernate create my tables, so I'm not 100% on this, but there is no reason to assume that Java's Float maps to MySQL's DECIMAL. In fact, according to the documentation, DECIMAL is an exact type while FLOAT and REAL are approximations. I believe Java's Float is an approximation, so this mismatch seems logical.

If you want to use MySQL's DECIMAL, try Java's java.math.BigDecimal instead of java.lang.Float.

answered Oct 10, 2011 at 12:29

jbrookover

5,1501 gold badge25 silver badges23 bronze badges

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

2 Comments

Thom Over a year ago

You're right about Java's float being an approximation. I should have thought about using BigDecimal myself. Let me work on this. What would I have used in my DB to match to float? Also, it's MS SQL Server not MySql.

Thom Over a year ago

After changing to BigDecimal, I got: Wrong column type in PsDb.dbo.Sensor for column FIELD1_CALIBRATION_OFFSET. Found: decimal, expected: numeric(19,2) So I looked up my hibernate mappings and did: @Column(name = "FIELD1_CALIBRATION_SCALE", columnDefinition="decimal", precision=4, scale=3) private BigDecimal field1CalibrationScale;

andreico · Accepted Answer · 2016-03-18 15:37:26Z

11

I've ran into this problem myself, using Jboss 7 and MSSQL.

I believe @The Thom's answer is correct and deserves more exposure.

please note that name parameter is optional if your value has the same name as the database column.

@Column(name="myColumnName" columnDefinition="decimal", precision=18, scale=3)
private BigDecimal myColumnName;

answered Mar 18, 2016 at 15:37

andreico

1211 silver badge7 bronze badges

6 Comments

joel goldstick Over a year ago

This is really a comment on another answer. I don't think it should be posted as a question.

andreico Over a year ago

@joelgoldstick I didn't mean to post it as question, but more as an answer. Tom mentioned this solution in a comment to the above answer. I personally saw this post 2 times before I realized the answer to his initial question was hidden in a comment to the answer above.

joel goldstick Over a year ago

my mistake. I meand answer.

Thom Over a year ago

@andreico Thanks for the feedback. I have incorporated my answer into the question so that it's easier to find. Please upvote to raise the visibility.

Muneeb Mirza Over a year ago

This worked for my decimal(22,4) by doing precision=22, scale=4 for BigDecimal. Thanks man.

|

Collectives™ on Stack Overflow

Hibernate MS-SQL Wrong column type Found: decimal, expected: float

2 Answers 2

2 Comments

6 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

6 Comments

Your Answer

Sign up or log in

Post as a guest

Related