On Feb 7, 2008 2:51 PM, Jim Kingdon <[EMAIL PROTECTED]> wrote: > > INSERT INTO TABLE_X (<some columns>) SELECT <some columns> FROME TABLE Y > > Done. > > There are a few error handling cases in InsertSubselectTest, but > that's more a question of whether the message is good than anything > which should cause trouble in using this.
Awesome! I've been trying a few tests upgrading the version of Mayfly used by Mifos. The newer Mayfly code appears to be causing the Mifos test suite from trunk revision 12291 (latest as of right now) to run about 25% slower than when the current version of Mayfly we have installed (which appears to be a build from CVS on 06-JUL-2007 given the name of the file is "mayfly-20070706.jar") is used. The test I have been running is: a. update to rev 12291 b. run "ant run_test" on a server with almost naught going on except the build itself c. record time build took d. delete lib/mayfly*.jar e. place compiled Mayfly JAR from today's CVS HEAD in 'lib' dir f. run "ant run_test" again g. record time h. restore current Mayfly JAR i. repeat steps 'b' through 'h' I suppose it might speed up Mayfly if it were built without debugging info, but this seems like something we'd want in our unit tests so I'm a little torn. Anyway, here's what I've seen: New Mayfly JAR: 23 min, 33 sec Old Mayfly JAR: 18 min, 54 sec I'm going to run the test loop a bunch more times overnight to try and see if these results are anomalous. Any ideas why the new version might make Mifos unit tests run slower? (Mifos developers, here is the referenced thread from the Mayfly mailing list: http://thread.gmane.org/gmane.comp.db.mayfly.general/3/focus=4 ) -- Adam Monsen ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
