ActiveRecord failing with a default field value of blank

where it's generating a NULL for my non-specified field, and that's
breaking the constraint. To the best of my ability to figure it out,
the code that does the MailQueueItem.create has not in any way changed.

I'm hoping that somebody can say "Yes, version X of ActiveRecord now
behaves differently in that circumstance..."

I do remember some changes on how defaults on text columns on mysql
are handled. Does that sounds relevant ? Did your version of
activerecord change ? (if so from what to what ?)

Fred

Frederick Cheung wrote:

where it's generating a NULL for my non-specified field, and that's
breaking the constraint. �To the best of my ability to figure it out,
the code that does the MailQueueItem.create has not in any way changed.

I'm hoping that somebody can say "Yes, version X of ActiveRecord now
behaves differently in that circumstance..."

I do remember some changes on how defaults on text columns on mysql
are handled. Does that sounds relevant ? Did your version of
activerecord change ? (if so from what to what ?)

Fred

It appears that there was a mysql upgrade (5.0.45 to 5.0.77) on the day
in question, but IT tells me no rails or gem updates. But it doesn't
seem like a mysql thing, as the insert statements would be generated on
the Ruby side?

It's a mystery :(. I can fix it easily enough (I'm explicitly setting
all my fields now) but still, it'd be nice to know why it suddenly
changed.

It appears that there was a mysql upgrade (5.0.45 to 5.0.77) on the day
in question, but IT tells me no rails or gem updates. But it doesn't
seem like a mysql thing, as the insert statements would be generated on
the Ruby side?

I think this was a change in how show columns reported defaults - it's
mentionned in the release notes for 5.0.51 (http://dev.mysql.com/doc/
refman/5.0/en/news-5-0-51.html )

Fred