From: | Mark Murawski <markm-lists(at)intellasoft(dot)net> |
---|---|
To: | "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | pgadmin4 - Don't disable save button after failure while editing table |
Date: | 2017-01-24 21:18:55 |
Message-ID: | 421558b6-2030-4243-d4f4-6e8d458b123b@intellasoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
1)
While doing Table -> View Data, and inserting a new row:
If you get an error such as a primary key violation on a table that uses
a serial... you may have violation where id=1... and you may want to
retry because you know that id=2 is available... so the counter will
increase and your insert will succeed.
But right now you get the error and the save button is grayed out, so in
order to retry, you need to enter some silly change like add a space,
and then save.. and then once your row is in, delete the extra space.
2)
When you get an error that pops up in the corner, like the
aforementioned PK violation for instance, the text is not selectable,
and I can't copy and paste this error if i wanted to.
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Murawski | 2017-01-24 21:25:25 | pgadmin4 - Allow re-opening queries from the history |
Previous Message | Adrian Klaver | 2017-01-19 21:08:11 | Re: factor effecting performance of postgres |