Committed by Greg Sabino Mullane <[email protected]>
Spelling and clarify we don't set utf-8 if already there.
---
TODO.utf8 | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/TODO.utf8 b/TODO.utf8
index 5260bac..8324061 100644
--- a/TODO.utf8
+++ b/TODO.utf8
@@ -19,7 +19,7 @@ The logic for setting "pg_internal" when unspecified is:
- If "client_encoding" <> "server_encoding", or perhaps better yet if
the pg_setting("client_encoding") returns a different value than
- the default version for that setting, then we assuming that the
+ the default version for that setting, then we assume that the
client encoding choice is *explicit* and the user will be wanting
to get raw octets back from DBI, thus set pg_internal to 0.
@@ -27,7 +27,8 @@ The logic for setting "pg_internal" when unspecified is:
Immediately after the connection initialization completes, we will
check for the set pg_internal flag; if set, we issue a "SET
-client_encoding TO 'utf-8'" and commit.
+client_encoding TO 'utf-8'" and commit (unless the client_encoding
+is already utf-8 of course).
Proposal for an "encoding" DBD attribute interface
--
1.7.0.5
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.