Commit 8a9e3291 authored by Bruce Momjian's avatar Bruce Momjian

Add description:

<   Currently locale can only be set during initdb.
>   Currently locale can only be set during initdb.  No global tables have
>   locale-aware columns.  However, the database template used during
>   database creation might have locale-aware indexes.  The indexes would
>   need to be reindexed to match the new locale.
parent 3adba41a
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
Last updated: Sat May 7 00:38:02 EDT 2005 Last updated: Sat May 7 11:45:16 EDT 2005
The most recent version of this document can be viewed at The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -250,7 +250,10 @@ Multi-Language Support ...@@ -250,7 +250,10 @@ Multi-Language Support
* Add NCHAR (as distinguished from ordinary varchar), * Add NCHAR (as distinguished from ordinary varchar),
* Allow locale to be set at database creation * Allow locale to be set at database creation
Currently locale can only be set during initdb. Currently locale can only be set during initdb. No global tables have
locale-aware columns. However, the database template used during
database creation might have locale-aware indexes. The indexes would
need to be reindexed to match the new locale.
* Allow encoding on a per-column basis * Allow encoding on a per-column basis
......
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Sat May 7 00:38:02 EDT 2005 Last updated: Sat May 7 11:45:16 EDT 2005
</p> </p>
<p>The most recent version of this document can be viewed at<br/> <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>. <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
...@@ -238,7 +238,10 @@ first. ...@@ -238,7 +238,10 @@ first.
<ul> <ul>
<li>Add NCHAR (as distinguished from ordinary varchar), <li>Add NCHAR (as distinguished from ordinary varchar),
</li><li>Allow locale to be set at database creation </li><li>Allow locale to be set at database creation
<p> Currently locale can only be set during initdb. <p> Currently locale can only be set during initdb. No global tables have
locale-aware columns. However, the database template used during
database creation might have locale-aware indexes. The indexes would
need to be reindexed to match the new locale.
</p> </p>
</li><li>Allow encoding on a per-column basis </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.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment