[mike_miller]

When you close the DB connection, why does the SQL results stay? I’ve obviously finished using them. You are obviously persisting the result set somewhere, which is tying up memory.

Could we please have an option to clear the result sets when the connection closes?

Regards,

Mike.

PS :Yes todays word of the day is obviously. And also Scribble.

[Scott Anderson]

Mike,

When you close the DB connection, why does the SQL results stay? I’ve obviously finished using them.

Unfortunately, it isn’t obvious at all. 🙂 You see, you might be done *retrieving* them, but you might not be done analyzing them. For example, now that you have the information you might close your DB connection to free it up, but be intending to copy those results over to a spreadsheet or charting package for further analysis. For us to close the results as soon as the connection is closed would be akin to the Repository View removing all the tree information under HEAD, once you’ve synchronized, since you’re obviously done with that now as well.

Could we please have an option to clear the result sets when the connection closes?

An option to do this is certainly a valid enhancement request, and I”ve added it to our internal tracking system as such.

Thanks for your input and interest in MyEclipse.

[mike_miller]

Cheers for the reply, Point taken on the results might still be needed. But they do also persist if I close the view and then re-open it. Surely that means I’m done with it. I don’t use the DB explorer in the way you described I keep the connection open until I’ve completely finished. So, apologies for my blinkered view.

Keep up the good work and brilliant support.

[Scott Anderson]

Thanks Mike, we appreciate it!

[ocomsoft]

I have a request how about a feature like the Generate Hiberate Mapping item that would allow you to click on a table and generate a simple EJB CMP/BMP.

Regards

Scott Warren

[Author]

Posts