# New MySQL behaiour for :null =\> false

**URL:** <https://www.ruby-forum.com/t/new-mysql-behaiour-for-null-false/130940>\
**Category:** Rails\
**Created:** [March 4, 2008, 5:10pm UTC](https://www.ruby-forum.com/t/new-mysql-behaiour-for-null-false/130940 "2008-03-04T17:10:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![icedragon](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/3ec8ea/32.png) [@icedragon](https://www.ruby-forum.com/u/icedragon)\
**Post date:** [March 4, 2008, 5:10pm UTC](https://www.ruby-forum.com/t/new-mysql-behaiour-for-null-false/130940/1 "2008-03-04T17:10:16Z")

</div>

I have migrations like

t.string :name, :null =\> false

I’ve tried some of the latest MySQL versions and now when I create a new  
object Person.new the name property is nil. Before if i have :null =\>  
false it was empty string?

Do someone have some idea about this?