On 8/31/06, Kevin Galligan <[EMAIL PROTECTED]> wrote:
1) preserveDataModel on the tomahawk table. This is a pretty cool thing, as it keeps the data in the request. However, this is also bad, because it will attempt to serialize your dataset. Somebody correct me if I'm wrong, but will serializing that data cause the whole hibernate tree to be pulled down by reachability? Even if not, if you've accessed much of the data such that the proxys have pulled the db data, you're still going to serialize a lot of extra data. I don't think this is a problem if you turn on server side storage AND turn off serialization. Not sure what that does to replication if you try to run a cluster, though. Session replication requires serilization, so you would be right back where you started.
I use Cayenne not Hibernate, but this is mostly all still relevent. I use t:saveState on the backing list instead of perserveDataModel -- you have a lot more control and perserveDataModel has often seemed to me to cause some unexpected behavior. Depending on how Hibernate works, serializing doesn't have to be costly. For Cayenne, serializing a committed or hollow (faulted) object only serializes the ObjectID (primary key representation).
