I have some logging tables that log simple things like when someone visits a particular webpage or whenever someone attempts to login. So for login attempts, the following <set> might be within a Person hibernate mapping:

Maybe a hacker is trying a million passwords and so this table could have 2 rows with exactly the same entries. i don't want the hacker to get a MySQL exception! :), well maybe this example isn't the greatest, but other parts of my code with exactly the same situation are important for me to log duplicate rows.

How can I tell hibernate to allow 2 rows with the same data? I understand the limitations of then being able to update or delete these rows, this is purely for logging purposes. I'll read the rows in bulk.[/code]

This prevention of duplicates has to do set. Set by definition cannot have duplicate elements. Use a bag instead. It can allow duplicates

Thanks, I'll look into bags. I read a brief mention of bags, but had trouble finding the documentation on it... I'll look harder now.

Why is there almost no documentation about bags?? Aren't bags a pretty important concept in database operations? Is there a better way to log operations? Even the Bag class javadoc (http://www.hibernate.org/hib_docs/v3/api/org/hibernate/mapping/Bag.html) is completely void of any comments... The author is listed as Gavin King who, as I understand, left the hibernate project a long time ago.

Is hibernate still being actively maintained? I'm a bit concerned relying so much on a framework that isn't moving forward and is starting to have some serious limitations (like so many uses of int without an option for long when servers today are more than capable of using values > 2.1billion).