Apache Friends Support Forum

dear frinds,
I upgraded my xmapp to 1.7.7 but when i write latn 1 in phpMyAdmin SQL database table the recored in un english leters or even english it become viewed as hix laters.
is there a reson.
like
5265616420616e64207726974650d0a
is: Read and write

check the Master collation default.

did you run mysql_upgrade???
http://dev.mysql.com/doc/refman/5.0/en/ ... grade.html

Also did you export your databases and then re-import them???

Good Luck

I removed the first ap. then installed the new ap. and then emported the DB tables one by one.
But the system when I update It cast to BIONARY
The View is not.
I write with ANSI coding, and the View is with Hix, and the casting is Bionary.
but the main coding of my database is latn1

this picture will give you a view

And this is a copy of my table in this file
http://www.gulfup.com/X6p5kki2oavkf

Note this is a copy of it
-- phpMyAdmin SQL Dump
-- version 3.4.5
-- http://www.phpmyadmin.net
--
-- Host: localhost
-- Generation Time: Oct 10, 2011 at 08:02 AM
-- Server version: 5.5.16
-- PHP Version: 5.3.8

SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";


/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;

--
-- Database: `hiaih`
--

-- --------------------------------------------------------

--
-- Table structure for table `gradetype`
--

CREATE TABLE IF NOT EXISTS `gradetype` (
`Code` tinyint(3) unsigned NOT NULL,
`namear` varchar(100) COLLATE latin1_bin NOT NULL,
`nameen` varchar(100) COLLATE latin1_bin NOT NULL,
`UserID` int(10) unsigned NOT NULL,
`LastUpdate` int(10) unsigned NOT NULL,
PRIMARY KEY (`Code`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_bin;

--
-- Dumping data for table `gradetype`
--

INSERT INTO `gradetype` (`Code`, `namear`, `nameen`, `UserID`, `LastUpdate`) VALUES
(1, 'ÇáãæÙÝíä ÇáÑÓãííä', 'Official Employees', 1177, 1177),
(2, 'ÇáãÓÊÎÏãíä', 'Staff', 1177, 1177),
(3, 'ÇáÚãÇá Úáì ÈäÏ ÇáÃÌæÑ', 'Labors On Wages', 1177, 1177);

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

a4world wrote:`namear` varchar(100) COLLATE latin1_bin NOT NULL,

Why do you choose latin1 binary if you don't want to use binary encoding?

I add a table file for viewing as you had saw.
but the problim is not only in the crampy latters. it is in english to .
Most of how installed the new ver. on Arabic windows. have the saime problime .
even that I have Arabic and 6 more laguages on my system . but I have the problime tow.
in the apps that I make. every thing is the same OK and gode . but in phpMyAdmin the full tabel become mixed and scrambiled . Arabic, And English as will.
And about your asking, why am I using Latin1_bin. I allowys use it. and I'm not casting the phpMyAdmin is the one how is casting. that is the subject.
the view as it say it is UTF-8, but what I see is not

If you have UTF-8 encoded data, you need a UTF-8 collating sequence. Things will just not turn out right otherwise.

Usually, if you have character type data, and multiple languages; the choice is UTF8_general_ci

Many many things don't work right with UTF-8, by the way. So you will need to use text editors that directly support UTF-8, or your data will get screwed when working with it locally.

you might want to read this -
http://www.joelonsoftware.com/articles/Unicode.html

just my opinion, and I have been wrong before, but I don't know any other way to go at it.

Good Luck

No one have an answer to that, still I uses the prevuse vertion and it is ok. but this one nooooo.
I trayd using it one more on more than one pc but there is no defret, I used the UTF-8 and it is same as it is.
what is happning. whay oney in display of the full table.
Note: in update and Insert pages It works right

The answer is: Don't use latin1_bin. The new phpmyadmin on MySQL 5.5 shows this hix letters independend on the os (even on my german windows xp, these hix letters are shown).

The collate is just for correct sorting (why should you want to sort in binary representation?).
MySQL is showing the columns in binary representation, because thats the way MySQL saves your data. Thats the way it is sorted.
Use latin1_general_ci (case insensitive) if you don't want that (or latin1_general_cs which sorted case-sensitive like latin1_bin), or any other latin1 collation. Or use utf8_general_ci or any other utf8 collation.

There are many ways to get around that. I can't help you, if you don't want to