Skip site navigation (1) Skip section navigation (2)

Re: [pgAdmin III] #290: New features for editgrid

From: "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org>
To:
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: [pgAdmin III] #290: New features for editgrid
Date: 2011-04-17 13:23:23
Message-ID: 054.1118856f4fb743900944ec5faf43ca5e@code.pgadmin.org (view raw or flat)
Thread:
Lists: pgadmin-hackers
#290: New features for editgrid
----------------------+-----------------------------------------------------
 Reporter:  gleu      |       Owner:  dpage
     Type:  feature   |      Status:  new  
 Priority:  minor     |   Milestone:       
Component:  pgadmin   |     Version:  trunk
 Keywords:  editgrid  |    Platform:  all  
----------------------+-----------------------------------------------------

Comment(by gleu):

 It would be better if we can use the Query/Editor grid as in Delphi
 DBGrid.

 There is two states of the BLOB fields, first is empty (NULL), and the
 second is [BLOB] (filled with something). PGAdmin is very slow when I try
 to see a table with full of blobs, or long "text" (memo) fields. The
 Delphi kind solution is that we don't show the blob fields fully, only the
 state, or they are text type, only a limited size (100 char) with "...".

 Some editor dialog is needed for edit blob (or memo) fields. Most
 important functions are "SaveToFile", "LoadFromFile" and "Clear".

 Memo (text with undefined size) fields are editable by a dialog with a
 Memo control (TMemo, EditBox, I don't know what possible in the source).

 This is very basic function for better work with tables, edit long fields.

-- 
Ticket URL: <http://code.pgadmin.org/trac/ticket/290#comment:1>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

In response to

pgadmin-hackers by date

Next:From: Guillaume LelargeDate: 2011-04-17 13:44:10
Subject: pgAdmin III commit: Fix a crash when adding an index constraint
Previous:From: pgAdmin TracDate: 2011-04-17 13:21:39
Subject: Re: [pgAdmin III] #302: Add per-column collation support

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group