Forum Moderators: coopster
I put those in quotes because you have to remember that you are never looking straight into the DB. You are always accessing the DB with some sort of client, whether it's a web browser, a command line client, or some GUI client that connects to the DB. There are always at least three components at work here
- DB server
- underlying data
- client used to view data
Since it looks fine in one client and not another, you know that the data is fine and the server is functioning correctly, but one of your two clients is unable to display these characters.
An analgous situation occurs with images stored as BLOB fields. More often than not, whatever client you use to browse your DB and send queries will return a bunch of text gibberish when you select an image blob field. This isn't a problem, it just means that the client is incapable of rendering jpegs. Take that same data and send it to a browser with the proper MIME type header and you'll see an image. That said, send it to the browser with the wrong MIME type header and you'll just get gibberish. Same with a PDF stored as a BLOB.
So what you are seeing are not differences between the data in the DB and the data sent to the page - it's the same data. Rather, what this gibberish tells you is that one client (your servers/scipts/browser combo) can render that character set while another client (the default DB client packaged with your DB server) is not (either inherently or because of settings) able to handle arabic character sets.
So the first thing to ask is whether or not your client that you use to browse the DB can be set up to properly interpret and display the character set. If not, is there another client for your DB server that will?
I found the solution. it was by using ODBC.
try using it omoutop it may help you.