I'm using the technique where you open a transaction....and then close it with an app filter. I'm using the example code from the Caveat emptor app.




The problem I ran into (before I added the flush statement) was that database errors seemed to be ignore. If a user tried to add a duplicate record....the makePersistent method does not catch the error.

I solved this by adding the flush()...but I'm wondering if I've correctly solved the problem.

In other words...until you close the transaction (which I'm doing with an app filter) you don't get your error. Since you don't close the transaction in the "makePersistent" -- you don't catch the error until much later.

By adding "flush" I then get my error trapped they way I expect, but I'm wondering if I'm breaking something else -- something that I don't understand and will haunt me later.


Thanks,

Lee

No opinions on this? Surely I'm not the only one to run into this problem as I'm using code from the Caveat Emptor application.

Lee

You can flush anytime you want.

Thanks...wanted to be sure I wasn't breaking the "lazy" feature, where I can still access related values that haven't yet been queried from my jsp's. (not that I've used this feature yet).

Now, as far as technique -- is the flush() the right approach? Or should the same "app filter" that does the commit....somehow do the error handling?

Typically I try to handle errors where they occur...but with Hibernate not performing the sql until it absolutely has to, you are no longer in the code where the error occurs.

Lee