Tom Lane wrote:
> Magnus Hagander writes:
>> Tom Lane wrote:
>>> (Hmm, actually it looks like pg_dumpall hasn't got a -E switch,
>>> which seems like an oversight. So you need to fix your locale,
>>> or else use pg_dump directly.)
>
>> IIRC, you can't set the windows console to be UTF8.
>
> Ugh
Magnus Hagander writes:
> Tom Lane wrote:
>> (Hmm, actually it looks like pg_dumpall hasn't got a -E switch,
>> which seems like an oversight. So you need to fix your locale,
>> or else use pg_dump directly.)
> IIRC, you can't set the windows console to be UTF8.
Ugh. That seems to raise the pr
Tom Lane wrote:
> "Moshe Ben-Shoham" writes:
>> C:\Program Files\PostgreSQL\8.3\bin>pg_dumpall -U admint >
>> c:\temp\dbdump.sql
>> pg_dump: SQL command failed
>> pg_dump: Error message from server: ERROR: character 0xd595 of encoding
>> "UTF8" has no equivalent in "WIN1252"
>
> Apparently you h
"Moshe Ben-Shoham" writes:
> C:\Program Files\PostgreSQL\8.3\bin>pg_dumpall -U admint >
> c:\temp\dbdump.sql
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: character 0xd595 of encoding
> "UTF8" has no equivalent in "WIN1252"
Apparently you have WIN1252 set as the defa
Hi,
I have a database with encoding UTF-8 installed on Windows, and I try to
dump it using pg_dumpall, on the machine on which the database is
installed. I get the following error message:
C:\Program Files\PostgreSQL\8.3\bin>pg_dumpall -U admint >
c:\temp\dbdump.sql
pg_dump: SQL command fa
On Sat, Feb 17, 2007 at 03:12:44AM -0800, Bob Hunter wrote:
> ERROR: invalid byte sequence for encoding "UTF8":
> 0xe02031
> HINT: This error can also happen if the byte sequence
> does not match the encoding expected by the server,
> which is controlled by "client_encoding".
> CONTEXT: COPY , l
Hello,
I have just updated to postgres8.1 and have the
following problem. The first line of the "PostgreSQL
database dump"
says:
SET client_encoding = 'SQL_ASCII';
which is correct. However, the restore says:
ERROR: invalid byte sequence for encoding "UTF8":
0xe02031
HINT: This error can als
Albe Laurenz a écrit :
I am trying to remove accents from a string. I found a nice
solution for this on postgresqlfr, using the to_ascii()
function.
Now, the problem I have is :
mydb=# SELECT to_ascii(convert('abcdef', 'LATIN9'));
ERROR: encoding conversion from UTF8 to ASCII not supported
> I am trying to remove accents from a string. I found a nice
> solution for this on postgresqlfr, using the to_ascii()
> function.
>
> Now, the problem I have is :
>
> mydb=# SELECT to_ascii(convert('abcdef', 'LATIN9'));
> ERROR: encoding conversion from UTF8 to ASCII not supported
>
> Why i
Hi List !
I am trying to remove accents from a string. I found a nice
solution for this on postgresqlfr, using the to_ascii()
function.
Now, the problem I have is :
mydb=# SELECT to_ascii(convert('abcdef', 'LATIN9'));
ERROR: encoding conversion from UTF8 to ASCII not supported
Why is the c
jef peeraer schreef:
i never thought i would be bblocked by an encoding problem :-(
My database is in LATIN1 , i have entries like this in a table called
gemeenten
Column | Type | Modifiers
---+--+
Hi Jef,I use the prototype 1.4 to ajax some web pages. I have to encodeURI the post form data especial the string form value, otherwise the server will receive wrong encoding characters.If you can not see the query result in correct web page encoding, maybe the page container of this XUL ajax contr
jef peeraer wrote:
i never thought i would be bblocked by an encoding problem :-(
My database is in LATIN1 , i have entries like this in a table called
gemeenten
Column | Type | Modifiers
---+--+--
i never thought i would be bblocked by an encoding problem :-(
My database is in LATIN1 , i have entries like this in a table called
gemeenten
Column | Type | Modifiers
---+--+
id
On Aug 30, 2006, at 6:29 AM, Pantelis Natsiavas wrote:
In addition trying to make the same query through the query tool
of pgadmin, I receive the same answer and of course null results. I
don't know if it matters, but I am using Windows XP and PostgreSQL
8.1 with JDBC 3. I have checked ev
Hello, I am really new to PostgreSQL and I seem to have an encoding problem. I come from Greece and I would like to make queries using greek characters too. I chose to write my database using encoding UTF8 and everything worked just fine creating it, until I tried to make a query using g
Hej,
though there are a few posts in the mailing lists archive with similar or
the same error messages, I couldn't find a solution for my problem with psql
there. So here's my encoding issue: I'm using a fresh install of 8.1.3 on a
German Windows 2000. I have set the codepage (1252) and font (Lucid
Hi.
I'm receiving this error message:
invalid UTF-8 byte sequence detected
SET search_path TO administracao,public;
CREATE OR REPLACE FUNCTION inserirTela(text,text,text) RETURNS text AS '
DECLARE
sName ALIAS FOR $1;
sDesc ALIAS FOR $2;
cSist ALIAS FOR $3;
BEGIN
On 12/1/05, marcelo Cortez <[EMAIL PROTECTED]> wrote:
> i have problems with encodings
PostgreSQL case conversion functions is a little bit buggy.
(Especially for Latin-N and Unicode encodings.) I've prepared a patch
[1] to fix a similar problem for Latin5 encoding. It wasn't tested so
much but w
hi Tom , folks
how do i " You need to make sure that the database
locale
> matches what you want," ?
any pointer by appreciated
sorry for silly questions ;)
best
___
1GB gratis, Antivirus y Ant
--- Tom Lane <[EMAIL PROTECTED]> escribió:
> marcelo Cortez <[EMAIL PROTECTED]> writes:
> > i have problems with encodings
>
> You need to make sure that the database locale
> matches what you want,
> not only the encoding.
>
> See the "Localization" chapter in the docs:
>
http://www.postgres
marcelo Cortez <[EMAIL PROTECTED]> writes:
> i have problems with encodings
You need to make sure that the database locale matches what you want,
not only the encoding.
See the "Localization" chapter in the docs:
http://www.postgresql.org/docs/8.1/static/charset.html
reg
folks
i have problems with encodings
the scenario is:
database: CREATE DATABASE "testLatin"
WITH OWNER = owner1
ENCODING = 'LATIN9';
test table:
CREATE TABLE test
( nombre varchar(20))
WITH OIDS;
ALTER TABLE test OWNER TO marcelo;
data:
nombre
-
"maricón"
"ñañoso pícaro"
t
[EMAIL PROTECTED] (Andreas Seltenreich) wrote in message news:<[EMAIL
PROTECTED]>...
> Fritz Bayer schrob:
>
> > The problem is that alls the "ü" characters get displayed as "".
> >
> > Why is that so?
>
> This could happen when your locale isn't properly set up. If, for
> example, LC_CTYPE is s
Fritz Bayer schrob:
> The problem is that alls the "ü" characters get displayed as "".
>
> Why is that so?
This could happen when your locale isn't properly set up. If, for
example, LC_CTYPE is set to C, your pager thinks this character isn't
printable and tries to do something smart with it. You
Fritz Bayer wrote:
Hi,
when I enter the following SELECT into psql
select * from mytable where data like '%ü%'
I get a selection of a couple of rows.
The problem is that alls the "ü" characters get displayed as "".
Why is that so?
Probably something in your terminal setup. I always have endless t
Hi,
when I enter the following SELECT into psql
select * from mytable where data like '%ü%'
I get a selection of a couple of rows.
The problem is that alls the "ü" characters get displayed as "".
Why is that so?
fritz
BTW: I set client encoding to latin1 and the database stores data in
utf8
27 matches
Mail list logo