On Monday, November 25, 2002, at 08:08 PM, Stefan Arentz wrote:
I'd kill to have more test cases and especially performance test cases. I would love to have tests the spit out a XML file with timings. Then we could quickly determine the results of a change.And then create reports similar to the JUnit html output? Say a 'JBench' framework ... ?
Never heard of it... have you used it
Spec doesn't say much about synchronization other then everything must be synchronized at the end of tx. The code is very complex, which means it is poorly written.Is that what the spec says or just good design?What kind of access do we have to a Collection?No... add and remove should (are?) delayed until the context completes (invocation or transaction). They should be preformed as a batch, but that is another story.
iterator() - should only call the original SELECT query and then fetch a result when Iterator.next() is called or DELETE when remove() is used.
add() - should only do a optional SELECT On the PK to prevent duplicates and then INSERT
remove() - should only do a SELECT on the PK to find out if the object was part of the collection and then DELETE
All this CMR stuff is really complicated :-) I'm now looking at the code of plugins/cmp/jdbc/bridge/RelationSet.java, which seems like a good starting point for these kinds of optimizations.
-dain
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
