[pgadmin-hackers] Re: [pgAdmin III] #129: SQL syntax error when changing a parameter for a database, role/user and a function

2010-01-20 Thread pgAdmin Trac
#129: SQL syntax error when changing a parameter for a database, role/user and a function --+- Reporter: gleu | Owner: dpage Type: bug | Status: closed Priority

[pgadmin-hackers] Re: [pgAdmin III] #129: SQL syntax error when changing a parameter for a database, role/user and a function

2010-01-20 Thread pgAdmin Trac
#129: SQL syntax error when changing a parameter for a database, role/user and a function +--- Reporter: gleu| Owner: dpage Type: bug | Status: new Priority: mi

[pgadmin-hackers] SVN Commit by guillaume: r8163 - in trunk/pgadmin3: . pgadmin/dlg

2010-01-20 Thread svn
Author: guillaume Date: 2010-01-20 21:52:47 + (Wed, 20 Jan 2010) New Revision: 8163 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=8163&view=rev Log: Fix an SQL error when changing a parameter for a database, role/user and a function. Fixes #129. Modified: trunk/pg

[pgadmin-hackers] SVN Commit by guillaume: r8162 - in branches/REL-1_10_0_PATCHES/pgadmin3: . pgadmin/dlg

2010-01-20 Thread svn
Author: guillaume Date: 2010-01-20 21:28:42 + (Wed, 20 Jan 2010) New Revision: 8162 Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=8162&view=rev Log: Fix an SQL error when changing a parameter for a database, role/user and a function. Fixes #129. Modified: branches

[pgadmin-hackers] [pgAdmin III] #129: SQL syntax error when changing a parameter for a database, role/user and a function

2010-01-20 Thread pgAdmin Trac
#129: SQL syntax error when changing a parameter for a database, role/user and a function +--- Reporter: gleu| Owner: dpage Type: bug | Status: new Priority: mi

Re: [pgadmin-hackers] Two unrelated issues

2010-01-20 Thread Dave Page
On Wed, Jan 20, 2010 at 7:05 AM, Ashesh Vashi wrote: > >> > As long as I remember, we found that auto-completion does not work >> > properly >> > (not as expected in better manner) in the combo-box under GTK. >> > >> > Hence, we decided to make the combo-box read-only at that time, until we >> > g