Hello.
[mysqldump]
default_character_set = latin1
[EMAIL PROTECTED] wrote:
amazing.. I failed to see that in the last msg - but that seemed to do the
trick - The images appear correctly now.. is there anyway in my.cnf to tell
it to always use the command?? Thanks much for the
Thanks for all your help Gleb! I Appreciate all your hard work!
In a message dated 1/12/2005 5:31:19 AM Eastern Standard Time, Gleb Paharenko
[EMAIL PROTECTED] writes:
Hello.
[mysqldump]
default_character_set = latin1
[EMAIL PROTECTED] wrote:
amazing.. I failed to see that in the last
Hello.
Have you tried to perform the dump using --default-character-set=latin1
option and then restore data from it?
[EMAIL PROTECTED] wrote:
Hello, thanks for helping! Here is the output of the requested statements on
live database:
SHOW CREATE TABLE avatardata;
|
amazing.. I failed to see that in the last msg - but that seemed to do the
trick - The images appear correctly now.. is there anyway in my.cnf to tell
it to always use the command?? Thanks much for the help!
In a message dated 1/11/2005 4:48:27 AM Eastern Standard Time, Gleb Paharenko
Hello, thanks for helping! Here is the output of the requested statements on
live database:
SHOW CREATE TABLE avatardata;
| customavatar | CREATE TABLE `customavatar` (
`userid` int(10) unsigned NOT NULL default '0',
`avatardata` mediumtext NOT NULL,
`dateline` int(10) unsigned NOT NULL
Hello.
mysqldump usually produced
SET NAMES utf8
at the begining of the dump file. The clues may be in this. Send us
the output of such statements:
SHOW CREATE TABLE avatardata;
SHOW CREATE DATABASE 'put the name of the avatar database';
SHOW VARIABLES LIKE '%char%';
and your
Hi there,
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote on Thursday, January
06, 2005 7:19 PM:
Thanks for the reply! I show the following information for my DB,
and shows the same for both the 3.23 DB And the 4.18a DB
Field Type Collation
avatardata
Hi,
[EMAIL PROTECTED] schrieb:
Hi Tom,
Thanks for the reply! I show the following information for my DB,
and shows the same for both the 3.23 DB And the 4.18a DB
Field Type Collation
avatardata mediumtext latin1_swedish_ci
I pasted a data table from the
I have reinstalled the v3 RPM again to my system, and used one of my original
backups from that same version. In 3.23 there is no 'collation' field.. I
wonder if that is the problem?? I am going to change it to latein1_bin to see
what happens next..
Thanks! I'll let you know!
In a
Hi Dr.
The avatars still show fine on 4.18a -- but the problem occurs when I
actually do a dump and reimport the dump file. That's when something goes
array.. Kinda weird if you ask me.. I wish that vBulletin wouldn't actually
hard code the binary in a table, lol.. It's got me totally
Sorry, forgot the attachments. These are the same exact two avatars from the
same user, using my 3.23 backup, for the good avatar, then the 4.18 bad avatar
attachment: brokenavatar.jpegattachment: goodavatar.jpeg--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote on Thursday, January
06, 2005 4:57 PM:
Sorry, forgot the attachments. These are the same exact two
avatars from the same user, using my 3.23 backup, for the
good avatar, then the 4.18 bad avatar
Looks like a character set issue - what's the
Hi Tom,
Thanks for the reply! I show the following information for my DB,
and shows the same for both the 3.23 DB And the 4.18a DB
Field Type Collation
avatardata mediumtext latin1_swedish_ci
I pasted a data table from the bad avatar and the good avatar
13 matches
Mail list logo