<   Right now only one encoding is allowed per database.
>   Right now only one encoding is allowed per database.  For a partial
>   patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php.
This commit is contained in:
Bruce Momjian 2006-06-08 02:42:44 +00:00
parent 8a75c07626
commit 366231f42f
2 changed files with 6 additions and 4 deletions

View File

@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Wed Jun 7 21:08:40 EDT 2006
Last updated: Wed Jun 7 22:42:39 EDT 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@ -354,7 +354,8 @@ Multi-Language Support
* Allow encoding on a per-column basis
Right now only one encoding is allowed per database.
Right now only one encoding is allowed per database. For a partial
patch, see http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php.
* Support multiple simultaneous character sets, per SQL92
* Improve UTF8 combined character handling?

View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Wed Jun 7 21:08:40 EDT 2006
Last updated: Wed Jun 7 22:42:39 EDT 2006
</p>
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
@ -329,7 +329,8 @@ first.
need to be reindexed to match the new locale.
</p>
</li><li>Allow encoding on a per-column basis
<p> Right now only one encoding is allowed per database.
<p> Right now only one encoding is allowed per database. For a partial
patch, see <a href="http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php">http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php</a>.
</p>
</li><li>Support multiple simultaneous character sets, per SQL92
</li><li>Improve UTF8 combined character handling?