Re: CVS Commit by dpage: Allow query cancel/terminate
От | Dave Page |
---|---|
Тема | Re: CVS Commit by dpage: Allow query cancel/terminate |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E40C369E@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | CVS Commit by dpage: Allow query cancel/terminate (cvs@cvs.pgadmin.org) |
Ответы |
Misc topics
|
Список | pgadmin-hackers |
> -----Original Message----- > From: Andreas Pflug [mailto:pgadmin@pse-consulting.de] > Sent: 22 June 2004 16:13 > To: Dave Page > Cc: pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] CVS Commit by dpage: Allow > query cancel/terminate > > Dave Page wrote: > > > > >BTW, on the restore dialogue, the 'contents' tab doesn't seem to do > >anything useful (nor for that matter does the view button). > > > > > Did you select a valid file? It should retrieve (-l) the > contents for distinct selection and restoration of objects. > I'm trying to finish the gui for LinuxTag, not necessarily > implementing all detail stuff immediately. Will complete that > next week. I see what's happening. I dump things in text format more often than not, and that's what it's barfing on. I think that needs to be handled a lttle more cleanly when we release - perhaps check the file format before passing it to pg_restore, and if text, just load the first hundred lines or so for inspection. Whilst we're on that subject, most of my backups have .sql extensions - any objection to adding that as a defaul extension in the file open dialogue. Finally, on a vaguely related note, I think we need to do some re-factoring of the context and tools menus. Perhaps have a copy of the tools menu as a sub menu of the context menu, rather than a seemingly random inclusion of some items. Also, when items are active could do with some though - for example, you cannot access the server status when clicking a server node(!), only a database. Any thoughts? Regards, Dave
В списке pgadmin-hackers по дате отправления: