From: "Francesco R." <vivo@gentoo.org>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] mysql-4.1
Date: Thu, 20 Oct 2005 15:03:17 +0200 [thread overview]
Message-ID: <200510201503.17187.vivo@gentoo.org> (raw)
In-Reply-To: <4357203B.2060500@munat.com>
[sorry if this is duplicated, having some problems switching email
client]
Re: [gentoo-server] mysql-4.1
(Francesco R., Thu Oct 20 12:39:07 2005)
Alle 06:42, giovedì 20 ottobre 2005, Ben Munat ha scritto:
> I see that MySQL-4.1 has been marked stable... anyone have any
> warnings I should heed before undertaking the upgrade (from
Yes, I've spent some time with a user that had problem upgrading a phpBB
site.
first: a duplicate primary key, reproduce case below
========= failed insert ===========
DROP TABLE IF EXISTS `t1`;
CREATE TABLE `t1` (
`f1` varchar(50) binary NOT NULL default '',
primary KEY (`f1`)
) ENGINE=MyISAM;
/*!40000 ALTER TABLE `t1` DISABLE KEYS */;
LOCK TABLES `t1` WRITE;
INSERT INTO `t1` VALUES ( 0x686D6D),( 0x686D6DB2);
/*!40000 ALTER TABLE `t1` ENABLE KEYS */;
--ERROR 1062 (23000) at line 10: Duplicate entry 'hmm' for key 1
========= failed insert ===========
the duplicate key is "hmm" with "hmm²"
Another problem was MySQL importing truncated fields,
the fields where truncated at charachter with dieresis.
The solution here was to pipe the dump through iconv:
# iconv -f ISO-8859-15 -t UTF-8 dump.sql | mysql
The other problem was with php-4 and the well known connection charset
problem.
To be sincere we 've not solved the last one in a satisfing way, but
this is my fault, it's way too much time I've setted up my boxes to
work with php-5 and mysql-4.1.
> 4.0.25-r2)? Francesco, you still lurking?
>
> b
when having time ;-)
--
gentoo-server@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-20 13:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 4:42 [gentoo-server] mysql-4.1 Ben Munat
2005-10-20 4:49 ` Bertrand CHERRIER
2005-10-20 5:34 ` W.Kenworthy
2005-10-20 7:03 ` Dave Strydom
2005-10-20 6:51 ` W.Kenworthy
2005-10-20 13:16 ` Francesco R.
2005-10-20 13:42 ` Wolf Giesen
2005-10-20 13:55 ` Dark
2005-10-20 15:41 ` [gentoo-server] mysql-4.1, revdep-rebuild Wolf Giesen
2005-10-21 12:00 ` [gentoo-server] mysql-4.1 William Kenworthy
2005-10-21 13:15 ` Francesco R.
2005-10-20 13:03 ` Francesco R. [this message]
2005-10-21 3:18 ` Ben Munat
2005-10-21 4:55 ` Dave Strydom
2005-10-21 6:31 ` Ben Munat
2005-10-21 10:07 ` Francesco R.
2005-10-21 13:17 ` Francesco R.
2005-10-21 13:22 ` Lance Albertson
2005-10-22 12:11 ` Dave Strydom
2005-10-22 12:16 ` Dave Strydom
2005-10-22 13:26 ` Barry Marler
2005-10-22 13:31 ` Dave Strydom
2005-10-22 13:50 ` Lance Albertson
2005-10-22 13:55 ` Dave Strydom
2005-10-22 14:01 ` Craig Webster
2005-10-22 14:32 ` Luca Longinotti
2005-10-22 14:51 ` Craig Webster
2005-10-22 19:43 ` Francesco R.
2005-10-22 19:46 ` Craig Webster
2005-10-22 20:57 ` Francesco R.
2005-10-22 22:13 ` Luca Longinotti
2005-10-22 22:53 ` Petteri Räty
2005-10-22 17:00 ` Barry Marler
2005-10-23 20:37 ` [gentoo-server] routing bittorent radu herinean
2005-10-24 8:19 ` Wolf Giesen
2005-10-24 14:13 ` Marton Gabor
2005-10-22 19:46 ` [gentoo-server] mysql-4.1 Francesco R.
-- strict thread matches above, loose matches on Subject: below --
2005-10-20 13:40 Covington, Chris
2005-10-20 13:50 ` Dark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510201503.17187.vivo@gentoo.org \
--to=vivo@gentoo.org \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox