3

If the database uses UTF-8 encoding, can text from all human languages be properly stored and retrieved?

Are there any "gotchas" when dealing with non-English languages in a PostgreSQL database?

Working in Ruby on Rails and PostgreSQL 9.1.

Improve this question

3 Answers 3

Reset to default
4

In addition to Spidey and Kevin's points (use utf-8 in the client and an ENCODING 'utf-8' database, beware of differing collations), I strongly recommend tagging each text field with the language it is in if at all possible.

If you ever want to use full text search or any kind of linguistic analysis, it really helps to know which language each field is in. Full text search can't do root-word analysis etc unless it has a dictionary and suffix list for the text being indexed - and for that it needs to know the language.

Storing ISO 639 language codes is probably a reasonable choice.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

3

Different languages tend to order the same character strings differently, so be careful about the COLLATION when sorting.

http://www.postgresql.org/docs/current/static/collation.html

Improve this answer

Comments

2

UTF-8 can encode all Unicode codepoints, so yes, you won't have any problem at all. You'll need to connect with a UTF-8 connection though, and make sure your application also reads the output as UTF-8 encoded text.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.