Re: pgadmin3 - Crash on renaming
От | Guillaume Lelarge |
---|---|
Тема | Re: pgadmin3 - Crash on renaming |
Дата | |
Msg-id | 1356339575.2000.9.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | pgadmin3 - Crash on renaming (Thangalin <thangalin@gmail.com>) |
Ответы |
Re: pgadmin3 - Crash on renaming
|
Список | pgadmin-support |
On Sun, 2012-12-23 at 16:13 -0800, Thangalin wrote: > Hi, > > Note that pgadmin3 -v or pgadmin3 --version should show the version number; > double clicking on the About dialog should allow selection of the text. ;-) > I agree that we should have better command line options, and -v/--version should be there. On the About dialog, it would be nice to have. > Using: > > - pgadmin3 1.16.1 (built Dec 16, 2012, rev: REL-1_16_1) > - Linux jaguar 2.6.35-30-generic #54-Ubuntu SMP Tue Jun 7 18:41:54 UTC > 2011 x86_64 GNU/Linux > - Kubuntu 10.10 \n \l > > *Replicate* > To reproduce the bug: > > 1. pgadmin3 > 2. Expand Server Groups >> Servers >> server_name >> Databases >> > database_name >> Schemas >> schema_name >> Tables > 3. Right-click a table (e.g., *old_table*) that has a primary key with a > sequence (e.g., bigserial) > 4. Select Properties > 5. Set the name to: *new_table* > 6. Press Enter (do not click OK) to accept the new name > 7. Expand Sequences > 8. Right-click on the old table's sequence (e.g., *old_table_id_seq*) > 9. Select Properties > 10. Set the name to: *new_table_id_seq* > 11. Press Enter (do not click OK) to accept the new name > > *Expected Results* > pgadmin3 merrily continues allowing database changes, and the rename > succeeds. > > *Actual Results* > pgadmin3 disappears, but the rename succeeds. > I don't reproduce the bug. I get the "Expected Results". -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com
В списке pgadmin-support по дате отправления: