From: Robert M. <man...@te...> - 2002-01-09 02:30:58
|
I see that someone (smgf) checked in work on MockConnection in the "core" m= odule 9/19/2001. Yet it appears unfinished and is obviously not in the lat= est build posted 8/21/2001. Any idea when this will get released? What I = need to have is the ability to track close calls on multiple PreparedStatem= ents that are being prepared within a single method from the same Connectio= n. One thing that's missing in the current implementation is the ability= to associate close calls with a particular PreparedStatement (I guess usin= g the SQL as an index into the HashMap). Or maybe I'm totally off the Mark= and you can set me straight ?? Rob Manning |
From: Oskar H. <osk...@de...> - 2002-01-09 08:40:14
|
We here at DeCode inc. have already implemented multiple PreparedStatements for MockConnection and it is working fine. I have not been able to commit this code because I can't find any guidelines on how to do so. I posted a question to 'moc...@li...' but have not got any answer yet. Can anyone give me a hint on how to post this code. Regards Oskar H. -----Original Message----- From: moc...@li... [mailto:moc...@li...]On Behalf Of Robert Manning Sent: 9. januar 2002 02:28 To: moc...@li... Subject: [MO-java-dev] Multi Prepared Statement MockConnections I see that someone (smgf) checked in work on MockConnection in the "core" module 9/19/2001. Yet it appears unfinished and is obviously not in the latest build posted 8/21/2001. Any idea when this will get released? What I need to have is the ability to track close calls on multiple PreparedStatements that are being prepared within a single method from the same Connection. One thing that's missing in the current implementation is the ability to associate close calls with a particular PreparedStatement (I guess using the SQL as an index into the HashMap). Or maybe I'm totally off the Mark and you can set me straight ?? Rob Manning _______________________________________________ Mockobjects-java-dev mailing list Moc...@li... https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev |
From: Steve F. <st...@m3...> - 2002-01-09 22:13:51
|
as you may have seen from the list, we've been a bit stuck recently and have just started on an overdue refactoring of the build. In theory, people should send changes to one of the committers and have them check it in, but we've been getting grossly behind. I have more time now and am intending to clear the backlog -- and to make the process easier. I suppose the obvious question is whether anyone out there would like to become an apprentice committer to spread the load? Steve ----- Original Message ----- From: "Oskar Hannesson" <osk...@de...> To: "'Robert Manning'" <man...@te...> Cc: <moc...@li...> Sent: Wednesday, January 09, 2002 8:39 AM Subject: RE: [MO-java-dev] Multi Prepared Statement MockConnections > We here at DeCode inc. have already implemented multiple PreparedStatements > for MockConnection and it is working fine. > I have not been able to commit this code because I can't find any guidelines > on how to do so. > I posted a question to 'moc...@li...' > but have not got any answer yet. > Can anyone give me a hint on how to post this code. > Regards > Oskar H. > > > -----Original Message----- > From: moc...@li... > [mailto:moc...@li...]On Behalf Of > Robert Manning > Sent: 9. januar 2002 02:28 > To: moc...@li... > Subject: [MO-java-dev] Multi Prepared Statement MockConnections > > > I see that someone (smgf) checked in work on MockConnection in the "core" > module 9/19/2001. Yet it appears unfinished and is obviously not in the > latest build posted 8/21/2001. Any idea when this will get released? What > I need to have is the ability to track close calls on multiple > PreparedStatements that are being prepared within a single method from the > same Connection. One thing that's missing in the current implementation > is the ability to associate close calls with a particular PreparedStatement > (I guess using the SQL as an index into the HashMap). Or maybe I'm totally > off the Mark and you can set me straight ?? > > Rob Manning > > _______________________________________________ > Mockobjects-java-dev mailing list > Moc...@li... > https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev > > > _______________________________________________ > Mockobjects-java-dev mailing list > Moc...@li... > https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev > |
From: Vincent M. <vm...@oc...> - 2002-01-09 22:28:19
|
Just a clarification to Steve's email so that there is no misunderstanding (hoping that it is not me who is misunderstanding it :-0 ). "In theory, people should send changes to one of the committers and have them check it in" Of course, this means sending the patches to the list (not to an individual committer) so that any committer who is available can help. It also lets other review the submitted code and comment on it (this is the principle of open source peer-review, as opposed to XP's pair-programming ;-) ) Now, some new committers would really be cool ! Becoming a new committer is simple : - send some patches to the list, - have them integrated in the code base, - send some more until the existing committers are fed up and give you direct write access to CVS ! Thanks -Vincent > -----Original Message----- > From: moc...@li... > [mailto:moc...@li...] On Behalf Of > Steve Freeman > Sent: 09 January 2002 21:58 > To: moc...@li... > Subject: Re: [MO-java-dev] Multi Prepared Statement MockConnections > > as you may have seen from the list, we've been a bit stuck recently and > have just started on an overdue refactoring of the build. In theory, > people should send changes to one of the committers and have them check > it in, but we've been getting grossly behind. I have more time now and > am intending to clear the backlog -- and to make the process easier. > > I suppose the obvious question is whether anyone out there would like to > become an apprentice committer to spread the load? > > Steve > > ----- Original Message ----- > From: "Oskar Hannesson" <osk...@de...> > To: "'Robert Manning'" <man...@te...> > Cc: <moc...@li...> > Sent: Wednesday, January 09, 2002 8:39 AM > Subject: RE: [MO-java-dev] Multi Prepared Statement MockConnections > > > > We here at DeCode inc. have already implemented multiple > PreparedStatements > > for MockConnection and it is working fine. > > I have not been able to commit this code because I can't find any > guidelines > > on how to do so. > > I posted a question to > 'moc...@li...' > > but have not got any answer yet. > > Can anyone give me a hint on how to post this code. > > Regards > > Oskar H. > > > > > > -----Original Message----- > > From: moc...@li... > > [mailto:moc...@li...]On Behalf Of > > Robert Manning > > Sent: 9. januar 2002 02:28 > > To: moc...@li... > > Subject: [MO-java-dev] Multi Prepared Statement MockConnections > > > > > > I see that someone (smgf) checked in work on MockConnection in the > "core" > > module 9/19/2001. Yet it appears unfinished and is obviously not in > the > > latest build posted 8/21/2001. Any idea when this will get released? > What > > I need to have is the ability to track close calls on multiple > > PreparedStatements that are being prepared within a single method from > the > > same Connection. One thing that's missing in the current > implementation > > is the ability to associate close calls with a particular > PreparedStatement > > (I guess using the SQL as an index into the HashMap). Or maybe I'm > totally > > off the Mark and you can set me straight ?? > > > > Rob Manning > > > > _______________________________________________ > > Mockobjects-java-dev mailing list > > Moc...@li... > > https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev > > > > > > _______________________________________________ > > Mockobjects-java-dev mailing list > > Moc...@li... > > https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev > > > > > > _______________________________________________ > Mockobjects-java-dev mailing list > Moc...@li... > https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev |
From: Steve F. <st...@m3...> - 2002-01-09 22:36:27
|
From: "Vincent Massol" <vm...@oc...> > Just a clarification to Steve's email so that there is no > misunderstanding (hoping that it is not me who is misunderstanding it > :-0 ). > > "In theory, people should send changes to one of the committers and have > them check it in" > > Of course, this means sending the patches to the list (not to an > individual committer) so that any committer who is available can help. > It also lets other review the submitted code and comment on it (this is > the principle of open source peer-review, as opposed to XP's > pair-programming ;-) ) sure, in practice I've been the only one committing for a while, so I just collapsed the format. S. |
From: Oskar H. <osk...@de...> - 2002-01-10 12:55:52
Attachments:
MockObjectsFromDecode.ZIP
|
OK ... great ... here are the changes we made to the MockObjects. (See attached zip file) List of changes * Support for validating multiple PreparedStatements executions pr. Connection. * The number of PreparedParameters are validated against the Prepared SQL statement. * PreparedStatements now supports the setNull(...) method * MockResultSetMetaData added. * MockResultSet.getString(int columnIndex) now converts all values to String. Changed files: com/mockobjects/sql/MockConnection.java com/mockobjects/sql/MockPreparedStatement.java com/mockobjects/sql/MockResultSet.java New files: com/mockobjects/ExpectationQueue.java (Used by the MockConnection class for PreparedStatement.) com/mockobjects/sql/MockResultSetMetaData.java com/mockobjects/test/TestExpectationQueue.java com/mockobjects/test/TestMockResultSetMetaData.java (This is not complete,I just implemented the methods I had use for.) com/mockobjects/test/TestConnection.java Hope you guys can use this. Regards Oskar H. -----Original Message----- From: moc...@li... [mailto:moc...@li...]On Behalf Of Steve Freeman Sent: 9. jan=FAar 2002 22:37 To: MockObjects Subject: Re: [MO-java-dev] Multi Prepared Statement MockConnections From: "Vincent Massol" <vm...@oc...> > Just a clarification to Steve's email so that there is no > misunderstanding (hoping that it is not me who is misunderstanding it > :-0 ). > > "In theory, people should send changes to one of the committers and have > them check it in" > > Of course, this means sending the patches to the list (not to an > individual committer) so that any committer who is available can help. > It also lets other review the submitted code and comment on it (this is > the principle of open source peer-review, as opposed to XP's > pair-programming ;-) ) sure, in practice I've been the only one committing for a while, so I just collapsed the format. S. =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Mockobjects-java-dev mailing list Moc...@li... https://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev |