FYI: Known bug in replication

2001-02-08 Thread Mayville, Jeffrey

I keep seeing users asking about a problem they are having with replication
(I ran into the bug myself). I saw a message a week or so ago acknowledging
the bug and noting that it was self-inflicted (while cleaning up code) and
has been corrected. The problem will not exist in the next release (.33).

The problem is that replication will fail if you stop and restart the slave.
The master.info file gets corrupted on the slave (added lines) so your IP
address and such are not read correctly and the slave cannot connect to the
master. In working to set up replication I also ran into the issue another
user noted of having the error log grow rather large. The longer you let it
grow, the bigger it gets (or that's how it seemed).

Is there a page where known issues with the current release are tracked? It
may be a good idea. That would hopefully alleviate repeated users asking
questions to this list about known issues (resolved or otherwise). I can
only imagine how discouraging it is when following this list to have to
respond to the same issues constantly.

A page with known issues and known workarounds (if any) could come in handy.

Jeff


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Problem with the UPDATE

2001-01-30 Thread Mayville, Jeffrey

"Guridi, Tomas" wrote:
 
 Hi , im having a strange problem with the update in mysql
 i have a table named "notices" with the following fields:
 
 id  :prymary, int, auto_increment.
 title   :varchar (255).
 priority:int.
 
 inside this table i have 5 registers like this :
 
 id  title   priority
 1   a   1
 2   b   2
 3   c   3
 4   d   4
 5   e   5
 
 now... to explain exactly what im doing y will write the exact querys im
 giving o the database.
 
 DELETE FROM notices where id=1
 UPDATE notices SET priority=priority-1 WHERE priority 
 1
 
 The result for this should be the following:
 
 id  title   priority
 2   b   1
 3   c   2
 4   d   3
 5   e   4
 
 The result im getting is :
 
 id  title   priority
 2   b   1
 3   c   1
 4   d   2
 5   e   3
 
 i have tryed everything,
 i foud that there was a problem with the update using the "WHERE
priority1"
 and they recommended using "WHERE priority+01"
 i also try that without having good results. the part that is even more
 strange is that if i run this querys from the console of the phpMyadmin
the
 result comes out rigth. i really dont know what to do.
 
 i am running on a NT 4.0 platform but i also try it on a REDHAT 6.2
platform
 having the same wrong result.
 if anybody could help please let me know.
 

I ran the script below on 3.23.32 on NT4 to try and duplicate your bug but
it works fine. Are the commands below the same as you are using?

--script start--
use test;
CREATE TABLE notices (id int auto_increment PRIMARY KEY, title varchar(255),
priority int) TYPE=MyISAM;
insert into notices (id, title, priority) values (1,'a',1);
insert into notices (id, title, priority) values (2,'b',2);
insert into notices (id, title, priority) values (3,'c',3);
insert into notices (id, title, priority) values (4,'d',4);
insert into notices (id, title, priority) values (5,'e',5);
delete from notices where id=1;
update notices set priority=priority-1 where priority1;
--script end--

Jeff

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php