MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Roger Baklund Date:August 20 2002 12:33pm
Subject:max_allowed_packet (was: Re: 4.0.x bug with LONGTEXT?)
View as plain text  
* Harald Fuchs
> In article <200208191407.g7JE71j12413@stripped>,
> Victoria Reznichenko <victoria.reznichenko@stripped> writes:
>
> > As you can see txt1 and txt2 contain text file ~ 8M
>
> > UPDATE tbl1 SET total=CONCAT(txt1,txt2) WHERE id=1;
>
> >  SELECT id, LENGTH(txt1), LENGTH(txt2), LENGTH(total) FROM tbl1;
> > +----+--------------+--------------+---------------+
> > | id | LENGTH(txt1) | LENGTH(txt2) | LENGTH(total) |
> > +----+--------------+--------------+---------------+
> > |  1 |      8390060 |      8390060 |             0 |
> > +----+--------------+--------------+---------------+
>
> > The same result.
> > MySQL inserts NULL in the total, because you can't store data more
> > than max_allowed_packet.
>
> Thanks for the clarification, Victoria.

I'm sorry, but this is not very clear to me...

The manual describes max_allowed_packet as "Max packetlength to send/receive
from to server".

Why are the columns transferred between server/client in the above
statement? Shouldn't  the entire UPDATE happen on the server side?

--
Roger

Thread
4.0.x bug with LONGTEXT?Harald Fuchs15 Aug
  • Re: 4.0.x bug with LONGTEXT?Victoria Reznichenko16 Aug
Re: 4.0.x bug with LONGTEXT?Harald Fuchs16 Aug
  • Re: Re: 4.0.x bug with LONGTEXT?Victoria Reznichenko19 Aug
Re: 4.0.x bug with LONGTEXT?Harald Fuchs20 Aug
  • max_allowed_packet (was: Re: 4.0.x bug with LONGTEXT?)Roger Baklund20 Aug
RE: max_allowed_packet (was: Re: 4.0.x bug with LONGTEXT?)Luc Foisy20 Aug
  • Re: max_allowed_packet (was: Re: 4.0.x bug with LONGTEXT?)Roger Baklund20 Aug
    • Re: Re: max_allowed_packet (was: Re: 4.0.x bug with LONGTEXT?)Victoria Reznichenko21 Aug
      • Re: max_allowed_packet (was: Re: 4.0.x bug with LONGTEXT?)Roger Baklund21 Aug