Conor, I think this is relevant - I had similar issue when I was saving reports to a db field. To work around, I changed the datatype of the field to :longtext. You can create or change the field to :longtext in your migration and everyone should be happy.
On Fri, Aug 13, 2010 at 12:58 PM, Conor Nugent <li...@ruby-forum.com> wrote: > I have a rails 3.rc app that I'm developing. I have a text entry in one > my models that can sometimes be quite big. I tried setting :limit => > 4294967296 on the text column in my migration file but this doesn't seem > to have any effect. The column is till created as a TEXT column rather > than MEDIUMTEXT or LONGTEXT. > > Does anyone have any idea why this might be happening? Is there a better > way of ensuring that > an entry won't default to TEXT in a mysql database? > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-t...@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com<rubyonrails-talk%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
