pls check this out:
http://linux-bangalore.org/2004/talks/shortlist1.php
kg
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
It looks a bit strange that CIDR output depends on datatype it has been
casted from:
fduch=# SELECT '1.1.1.1'::cidr;
cidr
1.1.1.1/32
(1 row)
fduch=# SELECT '1.1.1.1'::inet::cidr;
cidr
-
1.1.1.1
(1 row)
However these two seem to be 'equal' in terms of backend:
fduch
Hi, David,
On Thu, 11 Nov 2004 11:29:22 -0800
"David B" <[EMAIL PROTECTED]> wrote:
> show client_encoding gives:
> UNICODE
So is the data you send also encoded in unicode?
Maybe "set client_encoding latin1" or "\encoding latin1" helps.
HTH,
markus
--
markus schaber | dipl. informatiker
logi
David B wrote:
show client_encoding gives:
UNICODE
databases reads:
DATABASE OWNER ENCODING
OK - with the same settings here, I start psql and do:
\i unicode_import_test.txt
I get:
CREATE TABLE
t
-
AAA
À È Ð Ø
ZZZ
(3 rows)
In case this gets garbled by my email, the middle line cont
