> -----Original Message-----
> From: Roger Baklund [mailto:[EMAIL PROTECTED]]
> * Harald Fuchs
> > In article <[EMAIL PROTECTED]>,
> > Victoria Reznichenko <[EMAIL PROTECTED]> 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?
>
It probably does happen on the server side. But wouldn't it be smart to limit itself
to something it knows it can't transfer later?
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
