Today I tried to fix the remaining DbLoaderTst assertion failure (see bug
about isPrimaryKey) but in trying to do so quickly tumbled down the rabbit
hole..
- was the assertion failure in DbLoaderTst always there? There seem to be
several things wrong with DbLoader, not only the isPrimaryKey problem but
also other asserts seem to break 'sometimes'. I will definitely spend some
time on this tomorrow.
- what kind of DB setup do you guys use? PostgreSQL? mySQL? How long do
your test runs take on average? I have Oracle working but OHMYGOD is this
slow and RAM hungry - I can completely forget this on my work laptop
('only' 320 MB), and even on my new 2.4 GHz/512MB machine running eclipse,
Oracle 9i and the unit tests via ant on the command line completely bogs
down the whole machine. :(
- I saw that initial PostgreSQL support is there for the plugin, but it's
empty. Will this work for the tests or is this still under construction?
Would be sweet to get this to work because I have pgsql here and would
much prefer it to mySQL if possible.
- especially for running the tests hsqldb (http://hsqldb.sourceforge.net/)
might be worthwhile since it can keep tables in memory only (or on disk,
of course) and is therefore _extremely_ fast. According to a colleague it
'just works', can be embedded (single JAR) and is very easy to set up.
Might also be a good idea for reviewing the performance tests because
usually network latency and general RDBMS I/O randomness probably shadows
much of cayenne's behaviour.
- how can I control log4j output when running the tests? Maybe I
overlooked something but I couldn't find any way to specify this anywhere?
Makes debugging really hard..
thanks for pointers!
Holger
This archive was generated by hypermail 2.0.0 : Tue Nov 19 2002 - 18:07:49 EST