Hi!
I'm a hosting provider with several thousands of Mysql Databases under 4.0
version. I'm specially worried about TIMESTAMP format changes you did in
4.1. I'll have to update database server soon to have my systems updated.
I think that if i update my server version thousands of tables are
When mysql "had trouble starting up" what error messages did it give in
the .err file in the datadir?
-Eric
James Tu wrote:
I had to migrate from 4.0.11 to 4.1.12. I saved the data directory from the
older version. I also exported all the information using phpMyAdmin's export
tool. I have one h
I had to migrate from 4.0.11 to 4.1.12. I saved the data directory from the
older version. I also exported all the information using phpMyAdmin's export
tool. I have one huge .sql file.
When I upgraded to 4.1.12, I followed instructions to copy the contents of
the old data directory to the new
Hi!
On Apr 11, Christian Hammers wrote:
> Hello Sergei
>
> On Thu, Apr 07, 2005 at 03:14:10PM +0200, Sergei Golubchik wrote:
> > > I've just run into deep troubles while upgrading from 4.0.24 to 4.1.10a
> > > using precomiled Debian packages on Debian Woody although I read the
> > > comments rega
Hello Sergei
On Thu, Apr 07, 2005 at 03:14:10PM +0200, Sergei Golubchik wrote:
> > I've just run into deep troubles while upgrading from 4.0.24 to 4.1.10a
> > using precomiled Debian packages on Debian Woody although I read the
> > comments regarding upgrading on dev.mysql.com.
>
> > After start
Hello Sergei
On Thu, Apr 07, 2005 at 03:14:10PM +0200, Sergei Golubchik wrote:
> > I've just run into deep troubles while upgrading from 4.0.24 to 4.1.10a
> > using precomiled Debian packages on Debian Woody although I read the
> > comments regarding upgrading on dev.mysql.com.
>
> > After start
Hello
I've just run into deep troubles while upgrading from 4.0.24 to 4.1.10a
using precomiled Debian packages on Debian Woody although I read the
comments regarding upgrading on dev.mysql.com.
After starting the new server and running "mysqlcheck -r -v -A", I
experienced the following problems o
Hello.
As said at:
http://dev.mysql.com/doc/mysql/en/charset-conversion.html
You should avoid trying to convert directly from latin1 to the real
character set. If you have a backup, import a table from it. Check
that your character_set_xxx variables have a corresponding values.
See:
Hi..
I encountered some problems with character sets.
On the 4.0 version I stored UTF-8 strings. When upgraded to 4.1, I saw
the default character set was 'latin1', so I converted to UTF-8 using this:
ALTER TABLE my_table CONVERT TO CHARACTER SET 'utf8', DEFAULT CHARACTER
SET 'utf8';
When viewi
It's known bug, will be fixed in 4.1.2
- Original Message -
From: "Juri Shimon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Noor Dawod" <[EMAIL PROTECTED]>
Sent: Wednesday, December 17, 2003 12:37 PM
Subject: Re: Invalid ENUM values after up
I have the same problem with cp1251 and, seems, it's a bug. I have posted
correspoding message two days ago. Without any reply 8(((
I migrate 3.23.55 -> 4.1.1 and I don't know about existing such problem in
4.0.
Look in your .frm - your field is in correct charset. More of,
inserts and updates of
Hi,
I'm facing a problem with the new 4.1 branch.
I've built MySQL from sources with default-language=hebrew and
extra-languages=utf.
I've also used default-collation=hebrew_general_ci.
After installing, this is what I get for few of the variables:
mysql> show variables like '%char%';
+-
12 matches
Mail list logo
