I had my database set to SQL_ASCII and switched to UTF8, but now I
notice that I must add a slash for periods/dots ( \. vs . ) to insert
into varchar. Is this normal?
Thanks,
J
---(end of broadcast)---
TIP 5: don't forget to increase your free spa
PostgreSQL Admin wrote:
> I had my database set to SQL_ASCII and switched to UTF8, but now I
> notice that I must add a slash for periods/dots ( \. vs . ) to insert
> into varchar. Is this normal?
No.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end
I had the same problem when upgrading v7.4 database to v8, SQL-ASCII to UTF8 - we had to replace single backslashes with double backslashes in the v7 database to get the data to display correctly, then dump and restore in v8 / UTF8. Have we done something wrong please?
On 7/22/06, Peter Eisentraut
Well the server does have the capability to convert from the server encoding
to the client encoding and the other way around. To get this working you need
a server encoding which can be convertet to the clientencoding. UNICODE
(UTF8) is a good starting point here.
Now the server needs to know wa
