Dain Sundstrom wrote: > Marius Kotsbak wrote: > >> In that file, I find <fk-constraint>false</fk-constraint>. Is there >> a reason for that to be false as default? > > > > FK constraints are not supported by hypersonic, or more importantly I > couldn't get them to work. > > >> And since this one is there: >> <read-ahead> >> <strategy>on-load</strategy> >> <page-size>1000</page-size> >> <eager-load-group>*</eager-load-group> >> </read-ahead> >> <list-cache-max>1000</list-cache-max> >> >> , shouldn't most uses of CMPs be tuned OK (when using the same >> transaction!)? > > > > what? > > >> What does <list-cache-max>, and <time-out>300</time-out> mean? > > > > list cache max is the number of queries that the container will remember.
> When a query is executed, JBossCMP remembers the order of the > results. When lazy loading the container will read-ahead the next n > entities from the list. > > time-out has been renamed to read-time-out, and specifies the amount > of time that a read-only field is considered valid (milliseconds). I remember from using jboss 2.4.x, that manual changes in the DB would take some time to be reflected from CMP-beans (no new data even in a new transaction after the change), probably because jboss was caching the data, and not writing it to the DB at the same time the set-method was called. With jboss 3.x, I don't see this behavior. What has happened, what is the difference? Is there no write-cache now? Does it save one and one property of the beans? There should be a doc of the CMP-engine to answer these FAQs, at least a updated description of the settings in the DTD (the comments there doesn't explain it very well) > > -dain > > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
