And, in field_3 it was just word="f", so that shouldn't have added too
much. And, as I mentioned earlier, cutting the blob size down to 800K
also made it work OK.
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
You received this message because y
I've now worked it out.
I eventually decided to restart my computer on the off chance that MySQL
wasn't actually reconfiguring after I set max_allowed_packet (even
though it seemed this shouldn't actually affect things since I was only
changing from 1M to 32M, and my query seems to be less than
I just know that when we had that 'mysql has gone away' error, the mysql
logs had something like 'value too large for col' etc...
But if that isn't your problem, then I have nothing else to offer :(
On Wed, 10 Dec 2008 18:02:32 +0900, Farmer Schlutzenberg
<[EMAIL PROTECTED]> wrote:
>
> Hi S
Hi Simon,
I have it set on MEDIUMBLOB, which the MySQL documentation says has a
limit of 2^24 bytes, so well above 820K. It was previously on BLOB, and
I was getting a different error (something like "data too big for
column"). I just used :limit => size_limit as a condition in a rails
migrati
we have had the same problem and it turned out to be the size of the
column in mysql
whenever we create a blog column we go through and change the type to
LONGBLOB using the following in the migration.
execute "ALTER TABLE pgcs CHANGE pgc pgc LONGBLOB;"
Simon
On Wed, 10 Dec 2008 17:04:25 +
Actually, the variable in my my.ini file is max_allowed_packet, not
max_packet_size.
--
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
6 matches
Mail list logo
