Hibernate 3.1.3 has the following buggy behaviour. If a Session.saveOrUpdate() fails, the object being saved is still marked for saving. Thus, the next time Hibernate tries to synchronize with the data store, the save will be retried and (probably) fail again. The object should not be so marked until the application elects to explicitly try to save again. This appears to be fixed in Hibernate 3.2.
... until the collector arrives ...
This "blog" is really just a scratchpad of mine. There is not much of general interest here. Most of the content is scribbled down "live" as I discover things I want to remember. I rarely go back to correct mistakes in older entries. You have been warned :)
Blog Archive
-
▼
2007
(94)
-
▼
Jan 2007
(14)
- BIRT vs Script Extensions vs jTDS vs Eclipse Plug-ins
- Excel User-defined Worksheet Functions
- Building esi.execute
- Eclipse xdoclet Error
- SQL Server 2000 vs. Hibernate 3
- Hibernate Logging
- JDK Logging
- Eclipse Applications and JConsole
- log4j Logging
- Hibernate 3.1.3 Failed Saves
- Eclipse Java Compiler Bug
- Eclipse Java Compiler Non-Null Warnings
- Hibernate vs. Object.equals()
- IE7 vs. Automatic Windows Authentication
-
▼
Jan 2007
(14)