This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
That's true, although if your database doesn't support BLOBs, you can also use other "binary" types such as Oracle's RAW and LONGRAW. Even if the database does support BLOBs, I'm not sure that you gain anything by using them, since their main advantage over (say) a LONGRAW is that a BLOB allows you to update or retrieve only a portion of the data, and in the case of a serialized object instance, I can't think of any situation where you'd want to do so. Besides, if your database supports BLOB (which is a SQL3 data type), there's a good chance that it also supports structured data types (also defined in SQL3), and you'd probably be better off using one of those. There's some good information on SQL3 types at: http://java.sun.com/docs/books/tutorial/jdbc/jdbc2dot0/sql3.html Alternatively, you could pick up a copy of my book, which covers these topics in a bit more detail. ------------------ Brett Spell Author, Professional Java Programming [This message has been edited by Brett Spell (edited February 24, 2001).]
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com