# Why does db:schema:dump change float to double?

**URL:** <https://www.ruby-forum.com/t/why-does-dbdump-change-float-to-double/106920>\
**Category:** Rails\
**Created:** [June 15, 2007, 11:56am UTC](https://www.ruby-forum.com/t/why-does-dbdump-change-float-to-double/106920 "2007-06-15T11:56:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mahadewa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@mahadewa](https://www.ruby-forum.com/u/mahadewa)\
**Post date:** [June 15, 2007, 11:56am UTC](https://www.ruby-forum.com/t/why-does-dbdump-change-float-to-double/106920/1 "2007-06-15T11:56:16Z")

</div>

I have tables with double as their field’s datatype. When I ran  
db:schema:dump, Rails changed all of these double to float.  
I would like to know why, and if there is anyway I could preserve the  
datatype.

Thanks a lot,  
Chris

---

<div class="post-metadata">

**Author:** ![mahadewa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@mahadewa](https://www.ruby-forum.com/u/mahadewa)\
**Post date:** [June 15, 2007, 5:04pm UTC](https://www.ruby-forum.com/t/why-does-dbdump-change-float-to-double/106920/2 "2007-06-15T17:04:14Z")

</div>

Migrations do not support double data types to my knowledge. You  
would need to use database specific SQL to retain the double data  
type.

Michael

---

<div class="post-metadata">

**Author:** ![mahadewa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@mahadewa](https://www.ruby-forum.com/u/mahadewa)\
**Post date:** [June 15, 2007, 6:39pm UTC](https://www.ruby-forum.com/t/why-does-dbdump-change-float-to-double/106920/3 "2007-06-15T18:39:31Z")

</div>

Darn it ! Oh well.

Thanks a lot for your answer 🙂  
Chris