I've having hard time to find a good use case for it. Especially because
Index change is all about performance trades offs. And do you really
want your commercial transaction rollback because your index has fail?
Depends alot on what you are using the index for and what features the
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sqlserver-jtds-testsuite?log=log20061016021748
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:10/16/2006 02:17:48Time to build:Last changed:12/31/2005 20:44:14Last log entry:less noisy
What is DynamicBoost?
I use it for computing boost at runtime - not just a static boost number.Since my boost can depend on current state of different resources.For example - I need my articles that are new, pushed higher than the
old one's.public @interface DynamicBoost { float coef() default
Max Rydahl Andersen wrote:
Sidequestion:
How transactional is the index update in it self ? If you are indexing 10
objects after tx.commit() and
the 7th object fails to index does the 6 previous indexed objects go to
the index or are the rolled back ?
No the file system changes are not
The Hibernate developer team released Hibernate 3.2.0 GA today, this
release is now ready for production use. Please read the migration
guidelines if you are upgrading from an earlier version.
In addition to Hibernate Core, final releases of the Java Persistence
provider are now available
View results here -> http://cruisecontrol.jboss.com/cc/buildresults/hibernate-sqlserver-jtds-testsuite?log=log20061016215955
BUILD TIMED OUTAnt Error Message:build timeoutDate of build:10/16/2006 21:59:55Time to build:Last changed:12/31/2005 20:44:14Last log entry:less noisy
