RE: MySql error...

2005-03-08 Thread jschmidt
Hi, I don't have an answer for you yet - but I encountered exactly the same situation with one of my systems last weekend. Unfortunately, the error file sheds no light at all on the situation. In my case: [EMAIL PROTECTED] mysql]# cat JackFish.intechgra.com.err 050304 07:30:36 mysqld started

RE: MySql error...

2005-03-08 Thread jschmidt
: www.alchemetrics.co.uk Email: [EMAIL PROTECTED] -Original Message- From: jschmidt [mailto:[EMAIL PROTECTED] Sent: 08 March 2005 16:44 To: 'mel list_php'; [EMAIL PROTECTED]; mysql@lists.mysql.com Subject: RE: MySql error... Hi, I don't have an answer for you yet - but I encountered

Re: Replication and mysqldump issues

2003-09-19 Thread jschmidt
It looks like my first issue with slave replication is a verified bug #1345. I believe the second one is also because -Q does not quote db names so I opened a new bug #1348. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:

Replication and mysqldump issues

2003-09-18 Thread jschmidt
I have a database called abc-100 which seems to cause problems with replication and importing sql files created with mysqldump. First, if on the master we create a temporary table (because we don't have subselects yet) it causes the slave to die with the following. Relay log says: DROP /*!40005