Showing Different results in Datagrip than other client(psql) for Postgres
已计划
I am using Postgres and I have a strange problem. When I run a select query in datagrip, the result is different from the query when I ran through psql client.
Result from Datagrip
Result from Psql
If you look at has_not_tampered column, the result set is different.
Note that I have connected through same credentials and queried same table from both clients. No changes done in between.
I have run "Synchronize" and "Invalidate Cache and Restart" couple of times, but still the data is not refreshed.
Appreciate anyone who can point me in right direction.
请先登录再写评论。
I too am experiencing this. I really wanted DataGrip to work for me. I will not pay $25/mon for. a product that cannot return valid results from a simple query.
For reference, this is the query being run:
Here are the results from PGAdmin:
The results from DataGrip.
And finally. The results from DBeaver.
I'm getting consistent results from 2 open source FREE tools and cannot trust the results from a premium product. I am using and will continue to use the Professional versions of PyCharm and IntelliJ. Please fix this.
Hello! I have a similar problem with datagrip and postgres. I get different results from datagrip and psql for the same query. Explain me, please, how it's possible?
I use: DataGrip 2019.3.2; PostgreSQL (ver. 12.2); PostgreSQL JDBC Driver (ver. 42.2.5, JDBC4.2)
David W Vick,
It's strange.
Could you check you set transaction control to Auto and committed all transactions?
It would be great, if you can execute the same query in psql console and provide an output.
Hello David W Vick, @...
Sorry for slow response
I cannot reproduce the problem.
Could you please provide a self-contained example?
Also what version of DataGrip, Postgres and JDBC driver do you use?
Here is how you can check driver version:
1. Choose 'go to driver'
2. Here is the version
I am also running into this problem. Querying Redshift using DataGrip and comparing to SQLPro for Postgres. Same exact queries, different results. My colleague was using Datagrip and we were comparing our results, they are different (his results match what I am getting in SQLPro). So something funny is happening locally with my connection. I have tried restarting the app as well as updating the Redshift driver for DataGrip...
d.grebelny, Justin Portillo,
IDE(aka client) sets UTC timezone for the first connection(on data source creation) if you don't changed it on Options tab.
So, when you run query in client it uses client time zone, when you run query in psql - it uses server timezone.
So, is it supposed to adjust client time zone to server time zone? Or it's better to use local machine timezone?
Also, it looks like an issue https://youtrack.jetbrains.com/issue/DBE-3269. Could you post your answers there?
Yes, switching to UTC resolved the issue for me. Thanks!
@...,
Make sure you set transaction control to Auto and committed all transactions