Roger,
Tuesday, August 20, 2002, 5:34:25 PM, you wrote:
RB Maybe... :)
RB On the other hand:
RB 1) The documentation on max_allowed_packet talks only about transferring
RB data, not storing. (This should be easy to fix.)
Agreed..
RB 2) The mere existence of LONGBLOB and LONGTEXT suggests
* Victoria Reznichenko
RB 3) How can the server know that the max_allowed_packet for
RB _this_ connection
RB (the UPDATE'ing connection) isn't smaller than the
RB max_allowed_packet value
RB for a future SELECT connection? (I could do the UPDATE ...
RB CONCAT(... with
RB
* 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;
-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;
* Luc Foisy
-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)
Harald,
Friday, August 16, 2002, 5:46:20 PM, you wrote:
HF In article [EMAIL PROTECTED],
HF Victoria Reznichenko [EMAIL PROTECTED] writes:
Harald,
Thursday, August 15, 2002, 4:02:44 PM, you wrote:
[skip]
HF According to the manual, LOAD_FILE returns NULL if the file is too
HF large, but
Harald,
Thursday, August 15, 2002, 4:02:44 PM, you wrote:
HF I think I've found a bug in the handling of large INSERTs/UPDATEs
HF (MySQL 4.0.2, Intel/Linux).
HF Consider the following:
HF CREATE TABLE IF NOT EXISTS tbl1 (
HF id INT UNSIGNED NOT NULL AUTO_INCREMENT,
HF txt LONGTEXT
