OK, so here's my problem.
My application - a web-services application - uses a single DB-connection for each web-service through its lifetime.
Having a simple set of DML commands my code will be something like:
mDataAccessAdapter.OpenConnection();
mDataAccessAdapter.FetchEntity(...);
mDataAccessAdapter.SaveEntity(...);
.
.
mDataAccessAdapter.CloseConnection();
But when I need to create a new table among the DML commands, I understand that I should use either ODP directly (and open a new connection) or DataAccessAdapter.ExecuteActionQuery() (and create a new connection).
-
Is it true that in the ExecuteActionQuery case I wouldn't have to open the connection? What do the DataAccessAdapter perform behind the scene?
-
Why, anyhow, do I have to create a new connection object? Why can't the DataAccessAdapter's connection be used in some way?