On 8/31/05, Daniel John Debrunner <[EMAIL PROTECTED]> wrote: > Deepa Remesh wrote: > > > On 8/31/05, Philip Wilder <[EMAIL PROTECTED]> wrote: > > > > >>You did mention that the use of the Driver Manager was > >>problematic. The only reason that I use the DriverManager is so that I > >>can make use of the "jdbc:default:connection" rather then establishing a > >>new Connection. If you (or anyone else) knows a way in which I can do > >>this in a J2ME friendly manner then our problem is solved. If not, I can > >>take a closer look at my code and see how an additional Connection would > >>affect operation. > > > > > > I have changed the connection to use EmbeddedSimpleDataSource. So the > > procedure does not use nested connection and there is an additional > > connection. I am running tests with this change. I hope this is okay > > for the test. > > I would hesitate to make that change, procedures in general should be > using nested connections, use of another connection can lead to > deadlocks etc. The issue is that there is a chance people take test code > as an example of the correct way to write a procedure, and incorrectly > assume that use of EmbeddedSimpleDataSource does return a nested > connection. It may be better to move the test case to another test.
I will not submit this change then. I was thinking it should be okay to get an extra connection in a test. From what you say, I agree it is not a good practice. > > > Dan. > >
