From 5b50ede6706b5b2e9686208c49124e92f6f10bd3 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Wed, 14 Jun 2006 18:47:53 +0000
Subject: Add locale/encoding references:
< Right now only one encoding is allowed per database.
> Right now only one encoding is allowed per database. [locale]
> * Add CREATE COLLATE? [locale]
---
doc/src/FAQ/TODO.html | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 0ba00e3df42..9f67f384840 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
-Last updated: Wed Jun 14 14:39:03 EDT 2006
+Last updated: Wed Jun 14 14:47:40 EDT 2006
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -334,9 +334,10 @@ first.
need to be reindexed to match the new locale.
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. [locale]
http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php
+ Add CREATE COLLATE? [locale]
Support multiple simultaneous character sets, per SQL92
Improve UTF8 combined character handling?
Add octet_length_server() and octet_length_client()
--
cgit v1.2.3