Re: Bulk Upload.

2005-09-01 Thread Ramesh G
Hello All, I have a strange situation while doing Bulk upload (using LOAD DATA FILE). I have a database which has 60 records, when I try to insert 1 more records it is taking around 50-55 seconds to complete the task (I feel this is much higher than the normal timings). I notice a

Re: Read past Equivalent in MySQL

2005-05-13 Thread Ramesh G
I am using InnoDB only. But, it's not skipping locked rows. regards Ramesh On Fri, 13 May 2005 12:11:12 +0200, Martijn Tonies <[EMAIL PROTECTED]> wrote: Yes. Martijn is correct. I am trying to skip locked rows and get the next unlocked row available. Reading uncommited data will cause unexpect

Re: Read past Equivalent in MySQL

2005-05-13 Thread Ramesh G
Yes. Martijn is correct. I am trying to skip locked rows and get the next unlocked row available. Reading uncommited data will cause unexpected problems. I don't want to do that. Is there a way to do this? Regards Ramesh On Fri, 13 May 2005 11:54:11 +0200, Martijn Tonies <[EMAIL PROTECTED]> wrot

Re: Read past Equivalent in MySQL

2005-05-13 Thread Ramesh G
system could be as high as 500. Regards, Ramesh G On Fri, 13 May 2005 08:19:32 +0200, <[EMAIL PROTECTED]> wrote: Hi, you're ooking for the opposite of what can be done. One can select in share mode or for update : http://dev.mysql.com/doc/mysql/en/innodb-locking-reads.html this pr

Read past Equivalent in MySQL

2005-05-12 Thread Ramesh G
the same where clause. For the second instance of the query mysql seems to wait till the transaction of the first instance gets completed. This makes this query slow as the time taken for the transaction to complete is somewhere between 1 and 1.5 seconds. Regards, Ramesh G -- MySQL General