10 messages in com.mysql.lists.javaRE: How to store java objects in to t...
FromSent OnAttachments
va...@jenkon.com06 Dec 1999 15:07 
Ed Carp06 Dec 1999 15:10 
Hunter Hillegas06 Dec 1999 15:14 
Tim Endres06 Dec 1999 15:25 
dale welch06 Dec 1999 16:16 
Dirk Hillbrecht06 Dec 1999 16:22 
Cris Perdue06 Dec 1999 16:49 
va...@jenkon.com06 Dec 1999 17:06 
Cris Perdue06 Dec 1999 17:31 
va...@jenkon.com06 Dec 1999 21:03 
Subject:RE: How to store java objects in to the database
From:va...@jenkon.com (va@jenkon.com)
Date:12/06/1999 09:03:53 PM
List:com.mysql.lists.java

I guess one should go for storing Java objects (Hashtables) as Blobs into database if the Hashtable has large amount of data, if it has some what lesser data (i can not tell exactly, may be upto 1KB) one should go by creating another table with a foreign key. Any comments on this?

Thanks, Swamy

-----Original Message----- From: Cris Perdue [mailto:cr@perdues.com] Sent: Monday, December 06, 1999 5:32 PM To: va@jenkon.com Cc: ja@lists.mysql.com Subject: Re: How to store java objects in to the database

Thanks for your reply. Storing in a separate table with a foreign key is my first idea and easier for me, but doesn't it take more time to access data from some other table?

Performance is going to depend on various things. I wouldn't want to predict without knowning a good deal about your application.

To unsubscribe, send a message to the address shown in the List-Unsubscribe header of this message. If you cannot see it, e-mail java@lists.mysql.com instead.