Hi,

not sure if this is the best forum for this message, but there isn't an obvious one. This is more an FYI message than a request for help.

I've just upgraded from v2.1.5 to 2.1.6 and my tests reported an error. I tracked it down to a change in behaviour with the Criteria.createAlias method. A change that I could not see mentioned in the change log or elsewhere.

It is regarding calling Criteria.createAlias with the same arguments multiple times (eg. trying to create an alias of the same name twice). With 2.1.5 the call proceeded, with 2.1.6 a HibernateException is thrown with the error "alias already defined: <alias name>.

Calling createAlias more than once with the same arguements was obviously a bug in my code, and
I've changed it. This is for sure better than relying on the createAlias method to ignore the second (and subsequent) call. So this is not a problem. But, I thought it might be of use to someone to note this change in behaviour.

Jonny