I saw something like this as well. Using 4.1.2 made it go away. Try doing a
bk pull of the dev version of 4.1.2 and give it a go.
-steve--
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Victoria Reznichenko wrote:
[snip]
Could you create repeatable test case (table structure (output of SHOW CREATE TABLE) and text file with data that will be enough to reproduce the above behavior)?
I'll see if I can get something generic to error out. there's pretty
much no way I'll be able to se
mark warren bracher <[EMAIL PROTECTED]> wrote:
> heh, sometimes the obvious is right in front of you...
>
> I still can't get the full dataset to load with indexes on the table,
> but I _can_ apply indexes after the load. the indexes apply cleanly, so
> it doesn't seem to have been a data issue
heh, sometimes the obvious is right in front of you...
I still can't get the full dataset to load with indexes on the table,
but I _can_ apply indexes after the load. the indexes apply cleanly, so
it doesn't seem to have been a data issue. in any case, I can continue
prototyping.
it remains
In the last few days I've been doing some prototyping on mysql 4.1.1
(mainly because I want fulltext indexes against utf-8 data).
I have a table, artists_search_A, in which I want to load ~100K records.
My load process will routinely load 14783 records successfully. After
14783 inserts, any i
