From owner-freebsd-isp@FreeBSD.ORG Fri Aug 19 18:37:28 2005 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F1A816A41F for ; Fri, 19 Aug 2005 18:37:28 +0000 (GMT) (envelope-from mario@schmut.com) Received: from mail.schmut.com (dsl092-049-002.sfo4.dsl.speakeasy.net [66.92.49.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 4C07C43D64 for ; Fri, 19 Aug 2005 18:37:26 +0000 (GMT) (envelope-from mario@schmut.com) Received: (qmail 84052 invoked by uid 89); 19 Aug 2005 18:37:25 -0000 Received: from schmut.com (snoopy.schmut.com [192.168.23.1]) by snoopy.schmut.com (tmda-ofmipd) with ESMTP; Fri, 19 Aug 2005 11:37:20 -0700 (PDT) Received: from 192.168.23.8 (SquirrelMail authenticated user mario@schmut.com) by mail.schmut.com with HTTP; Fri, 19 Aug 2005 11:37:20 -0700 (PDT) Message-ID: <49542.192.168.23.8.1124476640.squirrel@mail.schmut.com> Date: Fri, 19 Aug 2005 11:37:20 -0700 (PDT) To: In-Reply-To: <20050819182023.4BFAE43D45@mx1.FreeBSD.org> References: <43061888.7040408@jpri.com> <20050819182023.4BFAE43D45@mx1.FreeBSD.org> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.9) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: mario X-Primary-Address: mario@schmut.com Cc: freebsd-isp@freebsd.org, james@jpri.com Subject: RE: migration from mysql 3.2.23 to 4.1.13 X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mario List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2005 18:37:28 -0000 So, Ruben Bloemgarten wrote: > Hi James, > > That was the first thing I tried, unfortunately that does not work as > the way 3.23 deals with ISAM is different to 4.1 and so it spits out > errors when it runs into unrecognizable syntax. If you have managed to > use mysqldump for a migration I would very much appreciate hearing about > it as it would simplify things conisderably. was this using mysldump 3.23 or 4.1? they produce different results and i found one to work and the other not. i don't remember which did what but just try the version you haven't yet. then there is also http://dev.mysql.com/doc/mysql/en/upgrading-from-3-23.html and then http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html looking at the docs, it seems, you need to do a bit more than just a dump. hope this helps. i remember going from 4.0 to 4.1 was already fun. mario;>