Re: file permissions problem on ALTER TABLE

2003-01-11 Thread miguel solórzano
At 10:17 11/01/2003 +0100, Dirkjan Ochtman wrote: Hi, server, I can DROP one of the tables, then I get the error again for the other table, so then I restart the server again and I can DROP the last table. The problem also persists on ALTERing TABLEs. Please if possible for you send me a tes

Re: file permissions problem on ALTER TABLE

2003-01-11 Thread Dirkjan Ochtman
Hi there, I still have problems with this when using MySQL 4.0.8. When I try to DROP a DATABASE, it will go through and delete all the tables, except the last two, apparently because it "can't delete the table.myi file". When I restart the server, I can DROP one of the tables, then I get the error

Re: file permissions problem on ALTER TABLE

2003-01-11 Thread Mark
: Saturday, January 11, 2003 12:31 AM Subject: Re: file permissions problem on ALTER TABLE > Hmm, okay, but isn't the 3.23 supposed to be stable and thus more bugless > than a gamma like 4.0.7? > > And also, I was wondering when 4 is going to be released as stable. > Looking over

Re: file permissions problem on ALTER TABLE

2003-01-10 Thread Manuzhai
8-3 > > - Original Message - > From: "Dirkjan Ochtman" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 10, 2003 7:40 PM > Subject: Bug: file permissions problem on ALTER TABLE > > > > > Hi there, > &g

Re: file permissions problem on ALTER TABLE

2003-01-10 Thread Stefan Hinz, iConnect \(Berlin\)
<http://iConnect.de> Heesestr. 6, 12169 Berlin (Germany) Tel: +49 30 7970948-0 Fax: +49 30 7970948-3 - Original Message - From: "Dirkjan Ochtman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 10, 2003 7:40 PM Subject: Bug: file permissions

Bug: file permissions problem on ALTER TABLE

2003-01-10 Thread Dirkjan Ochtman
> Hi there, > > I am using MySQL 3.23.54 on Windows XP (with SP1). Today, I encountered a > weird problem: when trying to ALTER a TABLE, MySQL said that it no > permissions to rename the *.myi file for that table. I kept encountering > this problem (trying to go from VARCHAR(6) to CHAR(6) for an in