I have never seen the need for this, but I like to understand things in case I ever run across them “in the wild”. I did see it in a commercial ecommerce application in which the designers serialized an “Order” object into a BLOB in an Oracle database table column.<\/p>\n
This avoided the overhead of a straight object relational mapper such as Hibernate or the ATG repository, so I guess that is a positive. In this case, they stored other columns such as the ORDER_ID for fast lookups, and then pulled the entire “object” back into the application server and de-serialized it.<\/p>\n
Below is an example:<\/p>\n
\r\nimport java.sql.*;\r\nimport java.io.*;\r\n\r\npublic class Order implements Serializable {\r\n int id;\r\n int quantity;\r\n int productId;\r\n Order (int id, int quantity, int productId) {\r\n this.id = id;\r\n this.quantity = quantity;\r\n this.productId = productId;\r\n }\r\n public static void main(String args[]) {\r\n try {\r\n Connection con = DriverManager.getConnection(\"jdbc:oracle:thin:foo\/bar@dbhost:1521\/dbservice\");\r\n PreparedStatement pst = con.prepareStatement(\"insert into orders values(?)\");\r\n for (int i = 1; i <= 1000; i++ ) {\r\n Order o = new Order(i,i,i);\r\n ByteArrayOutputStream baos = new ByteArrayOutputStream();\r\n ObjectOutputStream objOstream = new ObjectOutputStream(baos);\r\n objOstream.writeObject(o);\r\n pst.setBytes(1, baos.toByteArray());\r\n pst.execute();\r\n con.commit();\r\n }\r\n }\r\n catch(Exception e) {\r\n e.printStackTrace();\r\n }\r\n }\r\n}\r\n<\/pre>\nPulling it out of the database was done in a similar fashion, but is not shown here.<\/p>\n","protected":false},"excerpt":{"rendered":"
I have never seen the need for this, but I like to understand things in case I ever run across them “in the wild”. I did see it in a commercial ecommerce application in which the designers serialized an “Order”…<\/p>\n