If garbled code is not dead, continue to work hard ..

If garbled code is not dead, continue to work hard ..

I thought I had done a good job in dealing with Garbled text, but on this day I gave me a great deal of weight, which made me suffer, self-contained .....

The garbled characters I mentioned here are not only character encoding, but also the operating system and permission configuration for the dog blood.

First of all, the problem is like this: Because I encountered a problem of not recognizing Chinese characters when I used the mysqli extension library, I thought it was a small problem at first,, I thought it was wrong. When I set almost perfect character encoding, the problem still persists. I also know that the mysql client only recognizes gbk and changes it, there is no error in reading it. This process is a long process. The simulation data is viewed over and over again, but the results are the same.

It is reasonable to say that if I don't get this level, I should just close my hand. However, as soon as I thought, I would have provided three sets of databases, one old one is not decent, and this problem occurs again, if I had been away from it, it was not a problem. So I started to reinstall the environment. To make it easier, I tried almost all the integration packages and kept them unchanged .... It gave me a terrible idea to reload the system, no... Don't look for anything. Study it slowly.

I just want to ask what mysql can do, but mysqli can't, but at this moment, I found a more serious problem, and the database cannot be connected. Why should I do this to me, heaven is not fair ....

In the slow and painful process, I found a small way to modify the host file!

I found that the localhost connection was closed. I know the reason here. Why is there no problem in installing and using mysqli in other systems such as XP, the reason is that the file permission of the host is too high, which is also a concern of the win7 system. The configuration file is not correct, which leads to the above problem, that's so high that I can't directly operate it. Copy the copy and then modify it to move it in:

This is the worst thing:

#127.0.0.1 localhost
#: 1 localhost


#127.0.0.1 localhost

Delete # and you will be able to use it normally. In addition, we have already mentioned that set names gbk indicates the character encoding before data is inserted;

This data can be completely correct.

Note: The simulation data has been completed before, and the Appserver integration package is used here.

Struggle! Kid ....