risingwavelabs / risingwave

Best-in-class stream processing, analytics, and management. Perform continuous analytics, or build event-driven applications, real-time ETL pipelines, and feature stores in minutes. Unified streaming and batch. PostgreSQL compatible.
https://go.risingwave.com/slack
Apache License 2.0
6.89k stars 570 forks source link

Tracking: Integration with DataGrip #10347

Open neverchanje opened 1 year ago

neverchanje commented 1 year ago
neverchanje commented 1 year ago

Unsupported queries:

TennyZhuang commented 1 year ago

new bug

Failed to retrieve user types in dev.information_schema. [XX000] ERROR: ParseError: Bind error: failed to bind expression: pg_catalog.obj_description(t.oid, 'pg_type'). Caused by: Feature is not yet implemented: unsupported function: "obj_description" Tracking issue: https://github.com/risingwavelabs/risingwave/issues/112 Server SQLState: XX000. dev.information_schema. [XX000] ERROR: ParseError: Bind error: failed to bind expression: p.proargtypes. Caused by: Item not found: Invalid column: proargtypes
neverchanje commented 1 year ago

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.

neverchanje commented 10 months ago

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

neverchanje commented 9 months ago

Let's revive this issue as many users view Datagrip as the first option, although there are alternatives.

github-actions[bot] commented 3 months ago

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 no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean. Don't worry if you think the issue is still valuable to continue in the future. It's searchable and can be reopened when it's time. 😄