From: | Ulrich Meis <kenobi(at)halifax(dot)rwth-aachen(dot)de> |
---|---|
To: | jessica xingzc_he <xingzc_he(at)hotmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: persistence of java objects |
Date: | 2004-10-31 20:29:57 |
Message-ID: | 200410312129.57710.kenobi@halifax.rwth-aachen.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Sunday 31 October 2004 01:05, jessica xingzc_he wrote:
> hi,
>
> Does postgresql support this? if i want a column of a table for the
> persistence of instance of java objects, and use ResultSet.getObject() and
> ResultSet.updateObjecct() to access them. if so, what data type the column
> should be?
If you use a standard type like integer or varchar, you can do things like
setObject(1,new Integer(5));
setObject(2,"something");
which would be equivalent to
setInteger(1,new Integer(5));
setString(2,"something");
If you want to store complex objects in the database then they should
implement the java.io.serializable interface. Thereby you can store them in a
byteArray or push them into a bytearraystream and write the result with the
usual methods into the database.
A simple serialization example is here for java.io.File:
http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/examples.doc1.html
Regards,
Uli
From | Date | Subject | |
---|---|---|---|
Next Message | Ulrich Meis | 2004-11-01 02:41:28 | General Parser |
Previous Message | Dave Cramer | 2004-10-31 15:38:33 | Re: persistence of java objects |