On Thu, May 11, 2017 at 2:29 PM, Dave Page <dpage@pgadmin.org> wrote:
Ooops, managed to hit send too soon.
... it leads to failed updates such as:
2017-05-11 09:55:47,570: SQLpgadmin:Execute (void) for server #1 - CONN:2096775 (Query-id: 4540472):
UPDATE public.defaults SET
data_default_no_nulls = 'asas' WHERE
;
2017-05-11 09:55:47,577: ERRORpgadmin:
Failed to execute query (execute_void) for the server #1 - CONN:2096775
(Query-id: 4540472):
Error Message:ERROR: syntax error at or near ";"
LINE 3: ;
The new rows added is kept disabled untill grid is not refreshed.
On Thu, May 11, 2017 at 9:58 AM, Dave Page <dpage@pgadmin.org> wrote:
Hi
There seems to be couple of bugs in this;
- When creating a new row with my test table, if I click in the id column, don't change anything, then click in another column, the ID column value changes from [default] to [null], making it impossible to save that row with the default value. In this case I would expect it to stay at [default] unless I explicitly entered a value.
Fixed.
- When I add a new row, but leave the id as [default], the row is saved, but the [default] marker changes from gray to black (but only in the id column.
I forgot to add 'grey_color' class for numeric type fields. Now added.
- I'm able to edit a freshly added row immediately after saving but before refreshing. This shouldn't be allowed if we don't know what the primary key value is, as it leads to failed updates such as:
