diff options
| author | Mariusz Felisiak <mariusz.felisiak@mga.com.pl> | 2015-09-15 22:01:31 +0200 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-09-18 09:47:32 -0400 |
| commit | 6f1b09bb5c1bafe4633514cbff37f9a7ed7a63ae (patch) | |
| tree | bbf9a9e5d9b850d4ccaba2d768d243772047f951 /docs/ref/unicode.txt | |
| parent | 4b9d063da05faa112577a4e3cefd020850a25e9e (diff) | |
Made assorted improvements to the Oracle documentation.
Diffstat (limited to 'docs/ref/unicode.txt')
| -rw-r--r-- | docs/ref/unicode.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt index d4f560861f..f52076d2f7 100644 --- a/docs/ref/unicode.txt +++ b/docs/ref/unicode.txt @@ -23,11 +23,17 @@ able to store certain characters in the database, and information will be lost. * PostgreSQL users, refer to the `PostgreSQL manual`_ (section 22.3.2 in PostgreSQL 9) for details on creating databases with the correct encoding. +* Oracle users, refer to the `Oracle manual`_ for details on how to set + (`section 2`_) or alter (`section 11`_) the database character set encoding. + * SQLite users, there is nothing you need to do. SQLite always uses UTF-8 for internal encoding. .. _MySQL manual: http://dev.mysql.com/doc/refman/5.6/en/charset-database.html .. _PostgreSQL manual: http://www.postgresql.org/docs/current/static/multibyte.html +.. _Oracle manual: http://docs.oracle.com/cd/E11882_01/server.112/e10729/toc.htm +.. _section 2: http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch2charset.htm#NLSPG002 +.. _section 11: http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#NLSPG011 All of Django's database backends automatically convert Unicode strings into the appropriate encoding for talking to the database. They also automatically |