Open neverchanje opened 1 year ago
Unsupported queries:
[x] 1
SELECT
n.nspname,
c.relname,
a.attname,
a.atttypid,
a.attnotnull
OR (
t.typtype = 'd'
AND t.typnotnull
) AS attnotnull,
a.atttypmod,
a.attlen,
t.typtypmod,
a.attnum,
null as attidentity,
null as attgenerated,
pg_catalog.pg_get_expr(def.adbin, def.adrelid) AS adsrc,
dsc.description,
t.typbasetype,
t.typtype
FROM
pg_catalog.pg_namespace n
JOIN pg_catalog.pg_class c ON (c.relnamespace = n.oid)
JOIN pg_catalog.pg_attribute a ON (a.attrelid = c.oid)
JOIN pg_catalog.pg_type t ON (a.atttypid = t.oid)
LEFT JOIN pg_catalog.pg_attrdef def ON (
a.attrelid = def.adrelid
AND a.attnum = def.adnum
)
LEFT JOIN pg_catalog.pg_description dsc ON (
c.oid = dsc.objoid
AND a.attnum = dsc.objsubid
)
LEFT JOIN pg_catalog.pg_class dc ON (
dc.oid = dsc.classoid
AND dc.relname = 'pg_class'
)
LEFT JOIN pg_catalog.pg_namespace dn ON (
dc.relnamespace = dn.oid
AND dn.nspname = 'pg_catalog'
)
WHERE
c.relkind in ('r', 'p', 'v', 'f', 'm')
and a.attnum > 0
AND NOT a.attisdropped
AND n.nspname LIKE 'information\_schema'
AND c.relname LIKE 'tables'
AND attname LIKE '%'
ORDER BY
nspname,
c.relname,
attnum
[ ] 2
SELECT
n.nspname,
p.proname,
p.prorettype,
p.proargtypes,
t.typtype,
t.typrelid,
p.proargnames,
p.proargmodes,
p.proallargtypes,
p.oid
FROM
pg_catalog.pg_proc p,
pg_catalog.pg_namespace n,
pg_catalog.pg_type t
WHERE
p.pronamespace = n.oid
AND p.prorettype = t.oid
AND n.nspname LIKE 'pg\_catalog'
AND p.proname LIKE '%'
ORDER BY
n.nspname,
p.proname,
p.oid :: text
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
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 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. 😄