Replies: 5 comments
-
having extensively used the feature for years, "wrong" is not the adjective I'd use. I think you'll have to be more specific: sure the queries are different, but you should point out something that is correct on sql developer and wrong (not just different) on dbeaver. |
Beta Was this translation helpful? Give feedback.
-
Yes,you're right.But I remember that the previous version showed it right.I found that Dbeaver now has significantly fewer sessions,so I say it's wrong. |
Beta Was this translation helpful? Give feedback.
-
there are a couple buttons at the bottom to show background and inactive sessions. Background are excluded in sql dev according to your query, but maybe showing inactive does what you need? |
Beta Was this translation helpful? Give feedback.
-
On,yes!show inactive button looks like right!But the previous version showed all directly? |
Beta Was this translation helpful? Give feedback.
-
The previous version didn't show all directly. |
Beta Was this translation helpful? Give feedback.
-
System information:
Connection specification:
Describe the problem you're observing:
When I view oracle sessions in dbeaver,I found out it was wrong.It's different between oracle sql developer.
Steps to reproduce, if exist:
Double click sessions in oracle db view.
Include any warning/errors/backtraces from the logs
Dbeaver use sql:
SELECT s., sq.SQL_FULLTEXT, io.
FROM GV$SESSION s, gv$sql sq, gv$sess_io io
WHERE s.sql_address = sq.address(+)
AND s.sql_hash_value = sq.hash_value(+) AND s.sid = io.sid(+) AND s.inst_id = io.inst_id(+) AND s.sql_child_number = sq.child_number (+) AND s.TYPE = 'USER' AND s.STATUS <> 'INACTIVE'
Oracle sql developer use sql:
Check out it PLZ!!
Beta Was this translation helpful? Give feedback.
All reactions