Figured out what was causing it.... The /etc/my.cnf had a line in it, in the [mysqldump] section... compatible=mysql40
Comment that line out and it works - we need that when sending data to customers who are still running mysql40. Now I know whats causing it, I can work around it. Many thanks, Ian Collins. On 4/14/06, Imran Chaudhry <[EMAIL PROTECTED]> wrote: > > > The box that fails is running Redhat 7.3 (for customer backward > > compatibilty). I dont have any other 7.3 boxes to try - everything else > is > > newer. > > Was there a MySQL installation that came with 7.3 by default? If this > wasn't properly taken out of service, then you may be using an old > mysqldump with a newer server (or vice versa) and this may cause the > issue with autoincrement that you're describing. > > On the RH7.3 box can you issue these commands and tell me the results: > > mysqld -V > mysqldump -V > echo $PATH > > If these options are not taken, then can you confirm the mysqlserver > version by starting mysql client and typing status; > > I'm just reaching here, by I suspect that even though you have > upgraded to 4.1 over a default mysql install, your PATH still points > to the old mysql progs. > > -- > http://www.ImranChaudhry.info > MySQL Database Management & Design Services >
