[pgadmin-hackers] [pgAdmin III] #285: Memory leak in the edit grid that can occur if the user aborts a refresh of the data.

[pgAdmin Trac]

#285: Memory leak in the edit grid that can occur if the user aborts a refresh 
of
the data.
--+-
 Reporter:  dpage |   Owner:  dpage
 Type:  bug   |  Status:  new  
 Priority:  minor |   Milestone:   
Component:  pgadmin   | Version:  1.12 
 Keywords:  editgrid  |Platform:  all  
--+-


-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

[pgadmin-hackers] Re: [pgAdmin III] #285: Memory leak in the edit grid that can occur if the user aborts a refresh of the data.

[pgAdmin Trac]

#285: Memory leak in the edit grid that can occur if the user aborts a refresh 
of
the data.
--+-
  Reporter:  dpage|   Owner:  dpage   
  Type:  bug  |  Status:  closed  
  Priority:  minor|   Milestone:  1.12.2  
 Component:  pgadmin  | Version:  1.12
Resolution:  fixed|Keywords:  editgrid
  Platform:  all  |  
--+-
Changes (by gleu):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => 1.12.2


Comment:

 Fixed in
 
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=7fde85bb4ba06f930f0adcfc11c66387db9860d7
 and
 
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=b985162abc76fdd43ea6103fd44782a8a1ca5caa

-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [pgadmin-hackers] [pgAdmin III] #284: Logfile name is hard to adjust

[pgAdmin Trac]

#284: Logfile name is hard to adjust
--+-
  Reporter:  brsa |   Owner:  dpage  
  Type:  bug  |  Status:  closed 
  Priority:  minor|   Milestone:  1.12.2 
 Component:  pgadmin  | Version:  trunk  
Resolution:  fixed|Keywords:  logfile
  Platform:  windows  |  
--+-
Changes (by gleu):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => 1.12.2


Comment:

 Fixed in
 
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=7ec1239ef61f26181e92a64cb003786f34304a4f
 and
 
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=f12bcaae7d3eb309684f16663c1369760c6dca29

-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

[pgadmin-hackers] [pgAdmin III] #286: Fix date picker on GTK

[pgAdmin Trac]

#286: Fix date picker on GTK
-+--
 Reporter:  dpage|   Owner:  dpage
 Type:  bug  |  Status:  new  
 Priority:  minor|   Milestone:   
Component:  pgadmin  | Version:  trunk
 Keywords:  role |Platform:  linux
-+--


-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [pgadmin-hackers] [pgAdmin III] #286: Fix date picker on GTK

[pgAdmin Trac]

#286: Fix date picker on GTK
--+-
  Reporter:  dpage|   Owner:  dpage 
  Type:  bug  |  Status:  closed
  Priority:  minor|   Milestone:  1.12.2
 Component:  pgadmin  | Version:  trunk 
Resolution:  fixed|Keywords:  role  
  Platform:  linux|  
--+-
Changes (by gleu):

  * status:  new => closed
  * resolution:  => fixed
  * milestone:  => 1.12.2


Comment:

 Fixed in
 
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=e71ff77c0a21f11ca362f4ec368523dedf81c8b0
 and
 
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=a3ff1aa75d9ee6c03eb0ce082241c9273f63f0d0

-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

[pgadmin-hackers] [pgAdmin III] #287: Translation problem with SET STORAGE

[pgAdmin Trac]

#287: Translation problem with SET STORAGE
---+
 Reporter:  Hiroshi Saito  |   Owner:  Hiroshi Saito
 Type:  bug|  Status:  new  
 Priority:  minor  |   Milestone:   
Component:  pgadmin| Version:  trunk
 Keywords:  translation|Platform:  all  
---+


-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [pgadmin-hackers] [pgAdmin III] #287: Translation problem with SET STORAGE

[pgAdmin Trac]

#287: Translation problem with SET STORAGE
+---
  Reporter:  Hiroshi Saito  |   Owner:  Hiroshi Saito
  Type:  bug|  Status:  closed   
  Priority:  minor  |   Milestone:  1.14 
 Component:  pgadmin| Version:  1.12 
Resolution:  fixed  |Keywords:  translation  
  Platform:  all|  
+---
Changes (by gleu):

  * status:  new => closed
  * version:  trunk => 1.12
  * resolution:  => fixed
  * milestone:  => 1.14


Comment:

 Done in
 
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=6c0bbd89869939e1b48e9235c30d9601347316b8

-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

[pgadmin-hackers] [pgAdmin III] #288: Copy selected text to "Find:" text field

[pgAdmin Trac]

#288: Copy selected text to "Find:" text field
--+-
 Reporter:  Nail Samatov  |   Owner:  Nail Samatov
 Type:  feature   |  Status:  new 
 Priority:  minor |   Milestone:  
Component:  pgadmin   | Version:  trunk   
 Keywords:  querytool |Platform:  
--+-
 In many IDE's there is a very useful feature: if there is a selected text
 when a user has opened Find And Replace dialog, then this text is copied
 to the "Find:" text field. If there is no selected text, then "Find:" text
 field is not changed.

 I miss this feature in pgAdmin, so I attach the patch to fix it...

 May be it will be useful for someone else...

-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [pgadmin-hackers] [pgAdmin III] #288: Copy selected text to "Find:" text field

[pgAdmin Trac]

#288: Copy selected text to "Find:" text field
---+
  Reporter:  Nail Samatov  |   Owner:  Nail Samatov
  Type:  feature   |  Status:  closed  
  Priority:  minor |   Milestone:  1.14
 Component:  pgadmin   | Version:  trunk   
Resolution:  fixed |Keywords:  querytool   
  Platform:  all   |  
---+
Changes (by gleu):

  * status:  new => closed
  * platform:  => all
  * resolution:  => fixed
  * milestone:  => 1.14


Comment:

 Done in
 
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commit;h=a02a177e4468ff6c93d52aee0b8c282e09dcbd59

-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [pgadmin-hackers] Ticket 266: Unable to backup table when quotation marks used in the name

[Guillaume Lelarge]

Le 19/11/2010 14:47, Dave Page a écrit :
> On Thu, Nov 18, 2010 at 11:36 PM, Guillaume Lelarge
>  wrote:
>> Le 18/11/2010 09:08, Guillaume Lelarge a écrit :
>>> Le 18/11/2010 05:25, Ashesh Vashi a écrit :
 Hi Guillaume,

 As long as I do remember, the commandLineClenOption() function was
 introduced, because of the command-line parameter behaves differently with
 quote on different platforms.

>>>
>>> I figured that but there's no OS specific code.
>>>
 Though - I have tested your patch (Sorry - I do not have enough time to
 spend around pgAdmin now-a-days because of the work load).
 But It will be good - if you can please test the patch on all the platform
 (specially on windows) with quote in the name for table, user-name, etc
 before applying this patch.
>>>
>>> I did quite a lot of tests:
>>>
>>>  * on Linux
>>>
>>> ticket266=# \d
>>>  List of relations
>>>  Schema | Name | Type  |   Owner
>>> +--+---+---
>>>  S"1| TN5  | table | guillaume
>>>  S"1| tn2  | table | guillaume
>>>  public | T1   | table | guillaume
>>>  public | t"3  | table | guillaume
>>>  public | t2   | table | guillaume
>>> (5 rows)
>>>
>>>  * on Windows, much more but I don't have the list here (I created
>>>tables like t1, t"1, t "1, t" 1, t " 1, and the same for schemas)
>>>
>>> I'll try to have a set of tests to try on the different platforms.
>>> Unfortunately, I still can't test on MacOSX.
>>>
>>
>> I checked on Linux and Windows, and it works great on both. If someone
>> can try my patch on Mac OS X, you'll find attached a custom (-Fc) backup
>> of a small database with every kind of strangely named objects.
> 
> I tried backing up all the oddly named tables on OSX, and didn't get any 
> errors.
> 

So it works on each supported platform that I know of. Unless there is
tests I forgot to do, I'm inclined to commit this. Any last minute
objections?


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

[pgadmin-hackers] [pgAdmin III] #289: Foreign key UI bug

[pgAdmin Trac]

#289: Foreign key UI bug
-+--
 Reporter:  Aren Cambre  |   Owner:  gleu
 Type:  bug  |  Status:  new 
 Priority:  minor|   Milestone:  
Component:  pgadmin  | Version:  1.12
 Keywords:  foreignkey   |Platform:  all 
-+--
 I found a UI bug when creating a foreign key.

 When creating a primary key, all you have to do is select the column in
 the *Columns* tab of the dialog. You don't have to fill out any other
 fields; pgadmin appears to take care of this for you.

 It seems then that with a foreign key, all you should have to fill out is
 fill out the *References* field in the *Properties *tab, then in the
 *Columns* tab just select the relevant columns. If I do this and press OK,
 I get this error:

 *An error has occurred:*
 *ERROR: relation "fki_" already exists.*

 If I go back to the *Properties* tab and enter something into the *Name*
 field, then press *OK*, it works.

 The problem: I don't need to enter anything in the *Name* field of primary
 key dialogs, but I do with foreign key dialogs. Can it be consistent where
 I don't need to enter a *Name* field of the foreign key, either.

-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers

Re: [pgadmin-hackers] [pgAdmin III] #289: Foreign key UI bug

[pgAdmin Trac]

#289: Foreign key UI bug
-+--
 Reporter:  Aren Cambre  |   Owner:  gleu
 Type:  bug  |  Status:  assigned
 Priority:  minor|   Milestone:  
Component:  pgadmin  | Version:  1.12
 Keywords:  foreignkey   |Platform:  all 
-+--
Changes (by gleu):

  * status:  new => assigned


-- 
Ticket URL: 
pgAdmin III 
pgAdmin III

-- 
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers