Re: turning off autocommit in mod_plsql? (supporting transaction commit state across mod_plsql calls)

"Maxim Demenko" <mdemenko_at_arcor.de> wrote in message news:4458b8cf$0$4503$9b4e6d93_at_newsread2.arcor-online.net...
: Mark C. Stock schrieb:
: > i remember seeing an article on supporting transaction commit state
across
: > multiple mod_plsql calls, but can't seem to find the article
: >
: > i know this is possible, since the 'SQL Commands' window in HTMLDB/Apex
: > allows AUTOCOMMIT to be toggled on and off
: >
: > anybody know how mod_plsql supports this, so the same feature can be
: > implemented in a custom mod_plsql app?
: >
: > ++ mcs
: >
: >
:
: What i see in the docs is definitely opposite to your statement,
:

http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14337/concept.htm#sthref29
:
: By tracing a htmldb session i saw that piece however:
:
: =====================
: PARSING IN CURSOR #44 len=186 dep=1 uid=55 oct=47 lid=55
: tim=1119789769169787 hv=758058536 ad='299aedac'
: begin declare
: job number;
: begin
:

dbms_job.submit(job,'wwv_flow_sc_transactions.sc_job('||:SESSION||','''||:FLOW_USER||''');');
: :P1003_JOBID := job;
: :P1003_AUTOCOMMIT := 'Y';
: end;
: end;
: END OF STMT
: PARSE

#44:c=0,e=948,p=0,cr=0,cu=0,mis=1,r=0,dep=1,og=1,tim=1119789769169743
: =====================
:
:
: Best regards
:
: Maxim

I know, when I searched on mod_plsql transactions, I kept coming up with "This mechanism does not allow a transaction to span across multiple HTTP requests" -- but there was a paper or doc about 3 years ago or from oracle that explained how to configure mod_plsql to hndle transactions across HTTP requests. It may also have required some special coding of the procedures, though.

I'll post it or a link to it when I find it.

I did notice from V$SESSIONS that it looks like DBMS_JOB is involved for Apex's implementation. I wonder if they set up a daemon job of some sort?

++ mcs Received on Wed May 03 2006 - 09:15:30 CDT