I've seen such an error once, and found no good reason for it. Eventually I dumped the table to a text file, dropped it, and recreated it from the dump. The error did not recur. Probably was a nearly corrupt file
On Mon, 27 May 2002, Tzahi Fadida wrote: > The thing is, that the whole thing is dumb since the tables are very very small, i >am talking about > 3 tables of max 3kb. This is why i think it could be a bug. Anyway, i tried to give >an index to every > join but it did not change the outcome, same error. I find it strange since from >basic sql implementation, when you give an index to every join equality attributes it >should not use temporary space. Even if it would, that should not give me that error >since it should use external merge-sort algorithms that should work with even the >smallest of spaces. once again, making me suspect its some kind of a dumb bug.(it >could happen since as you know, large hostings like lycos take their time before >upgrading to newer versions) > p.s: i have 40mb free space on that account so external merge-sort algorithm should >work with np. > > * - * - * > Tzahi Fadida > [EMAIL PROTECTED] > Technion Email: [EMAIL PROTECTED] > Fax (+1 Outside the US) 240-597-3213 > My Cool Site: HTTP://WWW.My2Nis.Com > * - * - * - * - * - * - * - * - * - * > > WARNING TO SPAMMERS: see at http://members.lycos.co.uk/my2nis/spamwarning.html > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Herouth Maoz > > Sent: Sunday, May 26, 2002 9:31 PM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: RE: mysql error > > > > > > I attempted to reply earlier, but as several hours passed and it > > didn't come through, I am sending again. My apologies if it turns out > > to be a duplicate. > > > > At 17:40 +0200 on 25/5/2002, Tzahi Fadida wrote: > > > > > > > thought about it, but i can't control any of this from the lycos > > >web interface to mysql. > > > If you know how to do it, please add more details on how to add > > >this temporary space to > > > a user on mysql. > > > > > > > Well, I am afraid this is the wrong way to go about it. If that data > > is going to grow, you'll need to allocate more and more space. It's > > at times like this that you have to do some ugly "query tuning". > > > > In this instance, it would mean selecting the records, unordered, > > into a temporary table. Then selecting them from there, ordered. Then > > deleting the temporary table. > > > > If it's any comfort to you, I had the same sort of problem with > > Sybase at work, and the expert the company hired had recommended a > > similar solution. So it's not just a mySQL thing. > > > > Then again, if your data are going to stay the same size, you may > > keep on looking for the optimization information. How? RTFM - on my > > SuSE 7.3, the manual is in /usr/share/doc/packages/mysql. Note that > > you don't increase space per user. You change the parameters passed > > to the daemon. > > > > Herouth > > -- > > EMAIL: [EMAIL PROTECTED] > > HOME PAGE: http://herouth.port5.com/ > > > > ================================================================= > > To unsubscribe, send mail to [EMAIL PROTECTED] with > > the word "unsubscribe" in the message body, e.g., run the command > > echo unsubscribe | mail [EMAIL PROTECTED] > > > > > > > > > > > > > > > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > -- Thanks, Uri http://translation.israel.net ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
