Hibernate really misses the mark in this regard. A reasonable solution would be to mark that property as lazy, but then you have to do class post-processing to get it to work --- something that even the hibernate site recommends against (unbelievable!). The easiest solution is to store the bytes in a separate table and then the relationship is lazy loaded. TOPLink does not have this problem nor does Cayenne I believe (in case you want to switch).
Joel -----Original Message----- From: Chris Chiappone [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 17, 2006 3:20 PM To: Tapestry List Subject: [OT] Questions about Hibernate and large binary field Sorry this is a bit off topic but I have a question relating to hibernate in my tapestry application. I have a document object that contains a byte[] field to hold the actually file. It seems as though if the file is relatively large than any access to that object is extremly slow. Is there a work around to this? Or something that I may have missed when it comes to dealing with byte[] in hibernate? Thanks. -- ~chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
