[HACKERS] copy from stdin; bug?

2001-01-14 Thread Rehak Tamas

Hello

i don't know, whether it is a real bug or what, has been fixed or not, but
i can't find any info about it:

i try to fill my table from a file using copy from stdin and postgresql
corrupt the table. This happen if before the  or end of line there
is word that has a non-standard letter like o with accent and then an
ordinary lette [a-z]. and now i reproduced this error if that o is at the
and of the word. in these cases that word and the next one get into the
same field...

why does it happen?

thanks
tRehak


E-Mail: Tom Rehak <[EMAIL PROTECTED]>





Re: [HACKERS] copy from stdin; bug?

2001-01-14 Thread Rehak Tamas

Hi

On Sun, 14 Jan 2001, Tom Lane wrote:
> Sounds to me like a multibyte-character translation problem.  What
> encoding do you have set for the database?  What have you told it the
> client encoding is?

sorry, i forgot to write:
i use debian potato, i use the standard debian packege.
version 6.5.3

i haven't set any encoding i think it must be the default (?)
i used psql to copy the texts they are iso-8859-2 encoded...

please write if you need more information.

Udv
tRehak


E-Mail: Tom Rehak <[EMAIL PROTECTED]>





Re: [HACKERS] copy from stdin; bug?

2001-01-16 Thread Rehak Tamas

Hello

On Mon, 15 Jan 2001, Tatsuo Ishii wrote:
> Can you show me your database name and the output from 'psql -l'?

yes, here are the output:

datname  |datdba|encoding|datpath
-+--++-
template1|31|   5|template1
map  |  1003|   5|map
helyes   |  1003|   5|helyes

i found that if i put a space behind the letters ([o with
accent][a-z][\t]) before the tab, it works correct... but without the
space it corrupt the database...

Udv
tRehak


E-Mail: Tom Rehak <[EMAIL PROTECTED]>





Re: [HACKERS] copy from stdin; bug?

2001-01-17 Thread Rehak Tamas

Re

On Tue, 16 Jan 2001, Tatsuo Ishii wrote:
> The encoding of your databases are all UNICODE. So you need to input
> data as UTF-8 in this case. I guess you are trying to input ISO-8859-1
> encoded data that is the source of the problem. Here are possible
> solutions:
> 1) input data as UTF-8
:)

> 2) crete a new databse using encoidng LATIN1. createdb -E LATIN1...
yes, this will be the sollution...

> 3) upgrade to 7.1 that has the capability to do an automatic
>conversion between UTF-8 and ISO-8859-1.
i like to use deb packages and to use 7.1 i would have to upgrade to woody
(or even sid)...

thank you for your quick help!!!

Udv
tRehak


E-Mail: Tom Rehak <[EMAIL PROTECTED]>