-
Notifications
You must be signed in to change notification settings - Fork 637
Tracking: Integration with DataGrip #10347
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
Comments
Unsupported queries:
|
new bug
|
I personally feel that the ROI of Datagrip support is too low. It requires a lot of efforts to complete even its basic support, as it uses tons of Postgres advanced functions #2954 unnecessarily. If you don't disagree @TennyZhuang, I will temporarilly pause the development until we see a valid reason for continuation. |
Not planned for now as there are too many features to support. Please vote 👍 or comment to this issue if you feel that it's important to your use cases. Instead of DataGrip, our current recommendation is Beekeeper Community Edition |
Let's revive this issue as many users view Datagrip as the first option, although there are alternatives. |
This issue has been open for 60 days with no activity. If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the You can also confidently close this issue as not planned to keep our backlog clean. |
typinput
inpg_catalog.pg_type
#11689xmin
in pg_catalog.pg_namespace #14224The text was updated successfully, but these errors were encountered: