Hi,
Tip:
To identify what encoding you enter in the psql command interpreter:
1) Open a file with vim
2) Type in you SQL or copy/paste
3) Save the file and quit vim
4) $ file
Should give you the encoding of that text file.
For ex:
sf@orca:~$ echo $LC_ALL
en_US.UTF-8
sf@orca:~$ cat /tmp/xx
Hi all,
We have issues on HP with the libpq.so client library when doing networking.
It appears that psql is linked with libxnet.so, but not libpq.so ...
psql can connect to a remove PostgreSQL server, but a simple C program using
the libpq client library cannot, unless we link the program with
Tom,
I don't think so because the pg_class schema table shows an empty relation name
for the table created without double quoted identifier containing UTF-8 chars.
Seb
On 10/11/2012 04:03 PM, Tom Lane wrote:
Sebastien FLAESCH writes:
- I can use UTF-8 string constants in my queries.
-
ves me "UNICODE" - is this
the same as "UTF-8"?)
So is there a bug, or do I have to use a C collation and char type for UTF-8
databases on Windows?
I know that UTF-8 is not supported by the Windows C/POSIX library (setlocale,
and co).
Does it mean that it's not realisti
