Re: Multi-Threaded Oracle Clients

In article <3cruqk$r0r_at_pheidippides.axion.bt.co.uk>

           apgrace_at_jungle.bt.co.uk "Andrew Grace" writes:

> Can an Oracle client run multi-threaded?
>
> In my client code, I want to connect to the database once, then
> execute a number of non-blocking DML actions, with each action running
> in its own thread?
>
> Can the oracle server cope with having more than one concurrent request
> from the same login context?

Does this mean that you want the server to think that it has only one session connected, whilst that are actually several different DML statements running in parallel all with the same session id ?

If this _is_ what you want, then I feel that it ought not to be possible because of the possible ambiguities:

   if statement B starts after statement A (with no commits)

      Should it see none of the changes made by statement A
      Is the answer the same whether or not statement A has completed
      Is the answer the same whether or not statement A commits
      Should the parallel statements be allowed to do a commit 

On the other hand, if you actually want a single client program to run (transparently) multiple server sessions which only see each others changes after commits then this must be possible: lots of people have managed to do this by accident in (e.g.) Visual Basic by using Widgets and 'pass-through' in the same program.

-- 
Jonathan Lewis