[pgadmin-support] assert failed

2012-12-10 Thread Linos
Hi, today after i deleted and recreated in a query editor a constraint and went to refresh the constraints of the table in the browser i get an assertion error, i have attached the log generated. Regards, Miguel Angel. ASSERT INFO: ./src/generic/treectlg.cpp(201): assert "m_heightText != -1" fa

Re: [pgadmin-support] Helo

2012-12-10 Thread Raymond O'Donnell
On 09/12/2012 21:01, Sara Tan wrote: > Hello there, > > Would you please help me to solve this problem. I have installed > Postgresql 9.1, When I try to use PgAdmin to use it , I usually get this > message at the step. Please see the attachment to understand the problem. This means exactly what

[pgadmin-support] references combobox - order of object

2012-12-10 Thread Michal Kozusznik
When creating new foreign key, there is "references" combo-box in Columns tab. Can anyone say the rule used to sort the combo-box content? Because I'm embarrassed. See picture. I would like to see sorted items by schema and then by object name.   with re

Re: [pgadmin-support] [FEATURE REQUEST] select encoding for logs reader

2012-12-10 Thread Bartosz Dmytrak
Hi, In my case WIN1250 works "fine" - only works, but not fine :) Still, there is no option to change encoding of logs reader. Totally agree: DBs encoding (and log line) could be different, but this feature will give user option to try. Regards, Bartek

Re: [pgadmin-support] [FEATURE REQUEST] select encoding for logs reader

2012-12-10 Thread Dave Page
On Mon, Dec 10, 2012 at 8:25 AM, Bartosz Dmytrak wrote: > Hi all > I have a proposition of a new feature: select of encoding which is used by > logs reader in server status window. It looks like pgAdmin assumes UTF8, so > sometimes gives an error. > It is possible to read files with different enco

[pgadmin-support] [FEATURE REQUEST] select encoding for logs reader

2012-12-10 Thread Bartosz Dmytrak
Hi all I have a proposition of a new feature: select of encoding which is used by logs reader in server status window. It looks like pgAdmin assumes UTF8, so sometimes gives an error. It is possible to read files with different encoding via postgres: eg: SELECT convert_from(pg_read_binary_file('pg