You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you put an empty string as the input of a filter for an integer column you get this modal error message: Could not load table rows. The server said: invalid input syntax for integer: "".
Having an empty string as a filter makes of cause no sense, but this happens sometimes by hitting enter accidentally. Postico should just ignore these, not show an error message and load the rows as if no filter was set.
The modal dialog is even worse if it occurs in the foreign key row selector. The row selector closes immediately after the modal dialog sheet appears and there is no way of clearing the wrong filter. See attached gif:
It is also confusing to me that Postico remembers the filters for tables and the foreign key row selector indefinitely. Postico should limit this to the current window. It's annoying to first remove any old filters, if you open a table that you worked in a week ago.
The text was updated successfully, but these errors were encountered:
If you put an empty string as the input of a filter for an integer column you get this modal error message:
Could not load table rows. The server said: invalid input syntax for integer: ""
.Having an empty string as a filter makes of cause no sense, but this happens sometimes by hitting enter accidentally. Postico should just ignore these, not show an error message and load the rows as if no filter was set.
The modal dialog is even worse if it occurs in the foreign key row selector. The row selector closes immediately after the modal dialog sheet appears and there is no way of clearing the wrong filter. See attached gif:
It is also confusing to me that Postico remembers the filters for tables and the foreign key row selector indefinitely. Postico should limit this to the current window. It's annoying to first remove any old filters, if you open a table that you worked in a week ago.
The text was updated successfully, but these errors were encountered: