Yeah, that wouldn't fly in any of the apps that I work on. If you have
known constraints that the user is going to run into then you deal
with them in a friendly and helpful manner. Your end users aren't
going to find the generic tapestry error page friendly or helpful.
Josh
On Fri, Mar 14, 2008
doesn't T5 autoflush the hibernate session at the end of the page render,
though?
so either the user will see a valid page (and the transaction committed in
the database), or an error page (and no commits).
I hope so, as I'm trusting to this.
--nK
On Fri, Mar 14, 2008 at 5:07 PM, Josh Canfield
When you call session.save() your object is not necessarily getting
sent to the database, and thus database constraint violations may not
be thrown. If you want to ensure the object is sent to the database at
that point call session.flush() which "...is the process of
synchronizing the underlying p
