Hibernate-Guidelines - Revision history

Imifos: correct page category

2016-02-02T14:32:15Z

correct page category

2015-12-01T13:06:36Z

2009-04-20T11:08:06Z

‎Identify natural keys

2009-04-20T11:06:20Z

‎Don't use load() to determine existence

2008-11-05T18:46:25Z

‎Passwords in the hibernate.cfg.xml in plain text

2008-11-05T18:45:49Z

‎Simple

2008-06-05T18:41:18Z

2008-06-05T18:37:43Z

2008-06-05T16:32:37Z

‎Status

2008-06-05T16:31:45Z

@@ Line 77: / Line 77: @@
 *Map the properties of the natural key inside the <natural-id> element. Hibernate will generate the necessary unique key and nullability constraints, and your mapping will be more selfdocumenting.
 *We strongly recommend that you implement equals() and hashCode() to compare the natural key properties of the entity.
-*This mapping is not intended for use with entities with natural primary keys..
+*This mapping is not intended for use with entities with natural primary keys.
 Example in hbm.xml:

@@ Line 27: / Line 27: @@
 === Don't use load() to determine existence ===
-Do not use Session.load() to determine if an instance with the given identifier exists on the database; use Session.get() or a query instead.  This is a poss
+Do not use Session.load() to determine if an instance with the given identifier exists on the database; use Session.get() or a query instead.
 === Constructing Query Strings ===

@@ Line 42: / Line 42: @@
 === Passwords in the hibernate.cfg.xml in plain text ===
-Sensitive information such passwords should be encrypted to prevent attacks connecting directly to the database, you can extend Hibernate functionality to implement password encryption.
+Sensitive information such as passwords should be encrypted to prevent attacks like connecting directly to the database, you can extend Hibernate functionality to implement password encryption.
 ----

@@ Line 40: / Line 40: @@
 === Load mappings as resources  ===
 Deploy the mappings along with the classes they map.
 ----

@@ Line 9: / Line 9: @@
 === Transaction Scope ===
-All database communication should occur within the scope of a Transaction. Although we can't anticipate all design patterns, it would be an easy scan to flag jdbc and hibernate calls outside of transactions in a Hibernate application.
+All database communication should occur within the scope of a Transaction.
 === Persisting Tainted Data ===
-If an application sets tainted properties in an object, then makes that object persistent, it is highly likely that data will be accessed at some point and displayed.  If database values are never displayed to the user then obviously this is nullified.  Better yet if we could figure out which values from the db are tainted but I have a feeling it's not a feasible scan.  Long story short - saves, updates, inserts, whatever that are made with tainted objects should be flagged.
+If an application sets tainted properties in an object, then makes that object persistent, it is highly likely that data will be accessed at some point and displayed.  If database values are never displayed to the user then obviously this is nullified.  Better yet if we could figure out which values from the db are tainted but I have a feeling it's not a feasible scan.
 === Rollback ===

← Older revision		Revision as of 16:31, 5 June 2008
Line 333:		Line 333:
	query, while a query declaration inside a <class> element is made unique automatically by prepending the		query, while a query declaration inside a <class> element is made unique automatically by prepending the
	fully qualified name of the class, for example eg.Cat.ByNameAndMaximumWeight.		fully qualified name of the class, for example eg.Cat.ByNameAndMaximumWeight.
		+
		+	[[Category:Hibernate]]