Enhancement Request: Log Off button

[Harry MacDonald]

Not exactly of earth-shattering importance, but a button on the toolbar to log off the database (like the Session -> Close command in PL/SQL Developer) would be convenient. I often leave the query reporter client open, with an oft-used report loaded, for days at a time, and as a matter of practice I like to close the Db connections when I leave for the day.

Thanx,
HMD

 

[Marco Kalter]

I have added this to the list of enhancement requests. It may also be a nice enhancement to have a "log off after execute" option, so that you are only connected when the report is actually executing.

 

[Harry MacDonald]

Well, after being informed this morning that I had tied up a rollback segment on our data warehouse all weekend, I now realize that when I run a report in Query Reporter that includes a db-link, there is an implicit uncommitted trasaction created, and there is no way to either commit or rollback that transaction within query reporter short of logging off the database.

Since query reporter only does select statements (no updates), perhaps it would be a worthwhile addition to (optionally?) auto-commit on completion of the query, to release the holdback segment.

Thanx,
HMD

 

[Marco Kalter]

That would definitely be a good idea. Committing a select statement can never harm.

 

[Harry MacDonald]

The more I think about this, the more I think that Query Reporter should cache my logon credentials, and only open a database session when the query is executed (or when the query builder is activated), and close on completion. For situations where you want to avoid the overhead of making/breaking connections for a series of quick reports, an option to "maintain database connection between reports" could be included in the Options tab.

HMD

 

[Marco Kalter]

That is also a nice idea

 

[Harry MacDonald]

I know that you cured the "uncommitted transaction" issue when selecting over a db-link in PLSD version 6. Do you have an estimate when you might have a release of Query Reporter that solves that same problem, either with the auto logoff after execute or one of the other solutions we discussed above?

I'm getting flack from our DBA's because some of my query reporter users (Very happy campers, by the way - QR is a very valuable tool for us) don't log off after running cross-database reports, and we end up with inactive sessions maintaining table locks overnight and in some cases for days on end.

I know you said some time ago that you didn't expect any significant changes to QR until PLSD version 7 was released, but I would like to re-iterate my request for some way to release the lock(s) imposed by a db_linked select.

Thanx,
HMD

 

[Marco Kalter]

This will indeed be fixed in the Query Reporter version that is aligned with PL/SQL Developer 7. All select statements will implicitly be committed, and the Query Reporter can optionally log off after finishing a report.