:null => false, and MYSQL 5.0.x about transitions

[qoobaa]

Thanks for reporting the issue. I'll try to find some time to look at it (but it may not be easy to reproduce).

[Porta]

No problem. Let me know if I can help in any way.

[onknows]

Same here. I'm on MySQL 5.1 but I doubt that MySQL version is the problem. The problem is that the initial state is not set. The way it should work is that the first state should be used as initial state. At least that is what I understand from the documentation. Workaround is to specify the initial state in migration as the default value.

[qoobaa]

I don't use MySQL in my recent projects. Any volunteer to check/fix it?

[troessner]

@Porta , @ostraaten I can't reproduce this.
I set up a sample repo so that we can talk about the same thing: https://github.com/troessner/transitions_intial_state_bug

There is one migration with null: false : https://github.com/troessner/transitions_intial_state_bug/blob/master/db/migrate/20120526121122_create_orders.rb
with a very simple model here: https://github.com/troessner/transitions_intial_state_bug/blob/master/app/models/order.rb

In this project the initial state is set:

>> o = Order.new
=> #<Order id: nil, state: "fresh", created_at: nil, updated_at: nil>
>> o.state
=> "fresh"

you can easily see what I mean by:

git clone https://github.com/troessner/transitions_intial_state_bug
cd transitions_intial_state_bug
bundle install
bundle exec db:create db:migrate
rails c

and then do a

Order.new.state

I assume this issue has been fixed with unrelated commits.
I am closing this issue for now until somebody claims that this is still an issue for him and can give me clean instructions on how to reproduce that.