Re: Placing html entities into database?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Only one: if you plan to use more, than one character set. Say, you
> want store in one column text with greek, german, italian and chineese
> characters ;-)

The same column should hold english and german text. Acording to your reply this seems fine since there are no special characters in english?!

Thanx, Merlin


Viacheslav Kaloshin wrote:
On Tue, 08 Feb 2005 10:54:33 +0100, Merlin <news.groups@xxxxxx> wrote:

1 - use latest versions (4.1) of mysql and UTF-8 encoding.

I am using 4.0.18 and the data look korrekt when retriefed out of the database. I did not enable any kind of encodeing. Is there a downfall in how I am doing it, which I just now do not notice?


Only one: if you plan to use more, than one character set. Say, you
want store in one column text with greek, german, italian and chineese
characters ;-)

But if only one character set and no plans to extend - no problem to
use "as is" without any reencoding


Regards,

Merlin



2(bad) - before storing encode all string to base64 or something like this :-)

On Tue, 08 Feb 2005 10:29:20 +0100, Merlin <news.groups@xxxxxx> wrote:


Hi there,

I am wondering how to store special characters like the german ö for example
into a mysql db. Should the characters somehow be transforemd into html entities
like &ouml;? What are the benefits if it works without them as well?

Thank you for any hint,

Merlin

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



-- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php



-- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [PHP Users]     [Postgresql Discussion]     [Kernel Newbies]     [Postgresql]     [Yosemite News]

  Powered by Linux