RE: onstat -g sql

One of the reasons I ask this question is due to the fact when I do an onstat -g sql I have sessions with current queries, but onstat -g con shows them to be waiting on sm_read or netnorm.I thought that meant they were waiting for requests. Why would they wait for requests as well as have current queries? Will >===== Original Message From William Rice <ricew@operamail.com> ===== >My question is about Current SQL: > >I have always wondered what defined whether or not an SQL statement was >CURRENT. It seems for a select, it is their until I close my cursor. >But how about for an update or an insert? At what point (from the clients >perspective) does the SQL statement become Last Parsed and not current. > >Will > >------------------------------------------------------------ >This e-mail has been sent to you courtesy of OperaMail, as a free service from >Opera Software, makers of the award-winning Web Browser, Opera. Visit us at >http://www.opera.com/ or our portal at: http://www.myopera.com/ Your free e-mail >account is waiting at: http://www.operamail.com/ >------------------------------------------------------------