New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query failed when clicking foreign key cell in table view #330

Closed
stpe opened this Issue Feb 27, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@stpe

stpe commented Feb 27, 2017

When clicking a cell value in a column which is a foreign key to another table, the popup is not able to show that row in the table of the foreign key.

It fails with the following error:

Could not load table rows.
Query failed
PostgreSQL said: invalid input syntax for integer: ""

Screenshot:
https://dl.dropboxusercontent.com/u/20181/Screenshot%202017-02-27%2009.57.39.png

Happy to help debug it. (Is there an option to log/show the queries that Postico itself does?)

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Feb 27, 2017

Owner

Oh... this is a problem with the filter. You probably filtered by id, and the next time Postico opened the popover it cleared the filter value; now it tries to search for id = ''.

I'll have to make Postico smarter about this. In the mean time, click the "Clear" button to clear the filter.

Owner

jakob commented Feb 27, 2017

Oh... this is a problem with the filter. You probably filtered by id, and the next time Postico opened the popover it cleared the filter value; now it tries to search for id = ''.

I'll have to make Postico smarter about this. In the mean time, click the "Clear" button to clear the filter.

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Feb 27, 2017

Owner

To answer your second question, there is no query log for Postico, but that would be very useful in some cases!

Owner

jakob commented Feb 27, 2017

To answer your second question, there is no query log for Postico, but that would be very useful in some cases!

@stpe

This comment has been minimized.

Show comment
Hide comment
@stpe

stpe Feb 27, 2017

Ah, I see, now I understand why it behaves the way it does. Thanks for the quick reply and work-around.

Feel free to close this issue or turn into a feature request to make it smarter as you described.

stpe commented Feb 27, 2017

Ah, I see, now I understand why it behaves the way it does. Thanks for the quick reply and work-around.

Feel free to close this issue or turn into a feature request to make it smarter as you described.

@jakob jakob added the bug label Mar 7, 2017

@jakob jakob modified the milestone: v1.1.2 Mar 22, 2017

@jakob

This comment has been minimized.

Show comment
Hide comment
@jakob

jakob Jun 29, 2017

Owner

I've fixed this in build 1705.

You can download a prerelease version here: https://eggerapps.at/postico/builds/

Owner

jakob commented Jun 29, 2017

I've fixed this in build 1705.

You can download a prerelease version here: https://eggerapps.at/postico/builds/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment