My MySQL database is configured to use case insensitive searches.

session.load/get seems to re-use the key value for the object that is returned:

session.get(User.class, "bob").getName() returns "bob" even if the users.name primay key column in the database contains "BOB".

Hibernate saves on only fetching the other columns.

Can this behaviour be switched off somehow? I'd like to authenticate users case-insensitive with session.get() but then be able to use their correctly cased name.

Regards,

Andreas

I find this very hard to believe. Are you using a proxy?

Anyways you really shouldn't do something like that. Use a HQL query with lower(user.name) = "anything" and use a properly set up database.

I'm not using proxies. Here is an example:

User u1 = (User) session.load(User.class, "user");
User u2 = (User) session.load(User.class, "USER");
System.out.println(u1);
System.out.println(u2);
System.out.println(u1 == u2);

outputs:

User[name=user]
User[name=USER]
false

I think especially the u1 != u2 is a bug, because its the same row in the database.

Regards,

Andreas

Even if that is the case, I don't think Hibernate will be changed in a way to support a load with two different ids actually returning the same object. Don't know about the reuse part though ...

Then perhaps it should be noted in the documentation somewhere that Hibernate doesn't support case insensitive identities.

You can overide equals and hashCode of User class to fit your needs

Overriding equals and hashCode does not affect the behaviour of session.load() or the == operator.

No but the proper usage System.out.println(u1.equals(u2)) would work.

Still there is no persistent identity.

For persistent identity, you can safely use == as long both objects are loaded in the same Session (taken from the documentation).

Post it to JIRA please

Done.

See key HB-647.

http://opensource.atlassian.com/project ... key=HB-647