Is there ANY way to enforce a validation rule before execution of SQL queries that will still allow you access to the session (so you can perform queries, for example)?

I've been searching for a way to do this that is consistent for both save and update and I can't seem to find a good way to manage it.

I've had a look at ILifecycle and that seems like it will work for save and delete but onUpdate is not consistently called (for cascaded updates for example). :(

I've taken a look at IInterceptor but it seems that this will only allow access to the pipeline without providing access to the session. :?

Am I missing something? Has someone out there done what I'm trying to do and can provide some guidance?

Cheers,

Symon.

P.S. I'm more than happy for someone to give me a hint on how to hack the SessionImpl.cs to cause OnUpdate to be raised for cascaded updates or change Validate on IValidatable to be passed the session... :wink:

Hi

I'm also looking for a way to do this.

Any ideas?

In my example I need to check that a string is unique for the object, I guess that this kind of validation isnt unique, but I cant find the "best practise" to do this.