Message-ID: <3F8659C7.801@in.crimea.ua>
Date: Fri, 10 Oct 2003 11:03:35 +0400
From: Alexandr S <sasha@in.crimea.ua>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.5b) Gecko/20030901 Thunderbird/0.2
MIME-Version: 1.0
To: pgadmin-support@postgresql.org
Subject: Re: [BUGS] bug reporting
References: <3F7D8B18.3060108@in.crimea.ua>
	<3F7E046B.9060003@pse-consulting.de>
In-Reply-To: <3F7E046B.9060003@pse-consulting.de>
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 8bit

Next bug.
--with full russian version of Pgadmin 3.1 (with russian title of column 
and russian inserted data) :  there is problem when selecting, inserting 
relatively large block of data (for example , excerpt of some text about 
100 words size and more). Pgadmin suddenly ends to work and then I have 
to start pgadmin again, but fortunately data don t loose. And pgadmin 
don t export   any russian data to  *.csv or  *.dat  -  pgadmin 
suddenly  ends to work without saving any data. As I understood, there 
is patch that solve this problems, so  I hope new version of pgadmin 
will appear as soon as possible.
--with full english version of Pgadmin : this problems absent , but 
there is one thing that I don t understand and don t like me. When 
exporting relatively large block of data (text with, for example, 100 
words size) pgadmin saves to *.csv only little part of data  in the end 
of which follows ".." .  So pgadmin don t safe full content of row. Is 
it right behavior?  How can I safe full content of a row?
--when inserting large block of text , data often aligns along one long 
line, so its hard to view such data. It would be better if data take the 
form of sell like , for example, Pgaccess does.
 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Andreas Pflug wrote:

> Alexandr S wrote:
>
>> Pgadmin 3.1 don t work (operations like insert rows) with columns  
>> named in russian language (title of column in russian language). But 
>> the same operations using PhpPgAdmin - all works very  well, right. 
>> And if replace russian title of column with equivalent in english - 
>> all works very well.    PgAdmin responds the message: "2003-10-03 
>> 14:15:15 ERROR  : Column not found in pgSet: еще_колонка".  Operation 
>> System: Windows XP,  distribution binary (zip), language russian.
>>
> Hi Alexandr,
>
> you're on the wrong list, please use pgadmin-support for pgAdmin 
> related questions.
>
> Which tool did you use to insert the data?
>
> Regards,
> Andreas
>
>
>