I would second Quartz' request. I'm familiar with cascade from the SQL DDL side, but it was a little unclear figuring it out for Hibernate - the perspective seemed reversed.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gustavo 'Quartz' Hexsel Sent: Friday, January 23, 2004 4:00 PM To: [EMAIL PROTECTED] Subject: [Hibernate] Simple Suggestions Hi folks! I love the simplicity of your framework. Unfortunatly, it took me a long time to figure out what exactly was the consequence of each "cascade" declaration on the different types of relations. For instance, I didnt know whether cascade="all" in a many-to-many rel would delete the content of the relation table only, or include the other table as well. My suggestion would be to make a small table with the cascades options, the types of relationships, and put sample java/SQL codes and what would be deleted/updated/created, both in the DB and in the Java code (not always things get updated automatically!). I can do some of it myself, but I would have to make a test case for each situation, as I don't know the behaviour in most cases. Thanks for the excelent job! []s Quartz ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
