Re: Serialized data type for the Serialize code

Can you help me understand why you wouldn't know what the type was in the db
before you read it in?
I'm sure you have a valid reason; I just need some help to understand.

--dc--

----- Original Message -----
From: "Ken K" <kenmail(at)telocity(dot)com>
To: <pgsql-jdbc(at)postgresql(dot)org>
Sent: Saturday, May 26, 2001 9:58 AM
Subject: [JDBC] Serialized data type for the Serialize code

> Hi all,
>
> Before I start working on this code I would like to
> get any feed back from others who have worked with the
> Serialize package or have created custom data types
> in Postgres.
>
> Two problems with the current Serialize code are that
> you need to know the type of class stored before you
> can read it back and if the record with the oid field
> is deleted the serialized record the oid points to is
> not deleted.
>
> What I would like to do is create a new user defined
> data type for Postgres called serialized that would
> contain two oid', one pointing to the table for the
> serialized object and one pointing to the record in
> that table.
>
> I have never worked with user defined types in
> Postgres or with the JDBC. I suppose that in Java
> the serialized type would be implimented as a array
> of two integers.
>
> It does not seem that there is any way to fire
> rules or triggers on data types, so the user would
> still need to add triggers on tables that contain
> serialized fields to handle deletes and updates.
> Two generic functions could be created, though, that
> would handle all classes.
>
> Any comments on this idea?
>
> Thanks,
>
> Ken
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>