Handling Unique Key Constraints in NHibernate

[Mike]

Hello,
Can somebody point me in the correct direction on how to handle unique
key constraint violations in NHibernate? Is there a more optimized
way than simply querying the table before attempting the insert/
update?

Thanks!

[Jason Meckley]

the uniqueness exists at the database level, therefore you need to go
to the database to check.

If you can generally assume the object is unique, then you could
bypass the check, catch the unique constraint violation exception and
ask the user to submit their request again.

[Mike]

OK. Wasn't sure if NHibernate had any facilities to handle this
without having to catch an exception.