Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.oracle -> Re: acceptable way to program

Re: acceptable way to program

From: ByteCoder <ByteCoder_at_127.0.0.1>
Date: Fri, 31 Dec 2004 10:45:20 +0100
Message-ID: <33kldrF3u5jhoU1@individual.net>


steve wrote:
> Hi,
>
> Recently I have been looking at the various ways people are implementing,
> interaction between java & oracle databases.
>
> I was always instructed on the purity of the data model, "normalize the
> data" etc.
>
> I have seen people Serializing java objects , such as purchase orders
> orders, customer records etc , then sticking the "object" into am oracle blob
> column.
>
> finally when they want to retrieve it they de-serialize the object., work on
> it then re-serialize and stuff it back into the oracle blob.
>
> to me this causes the following problems:
>
> 1. the object can become very big, and can only be recovered in it's
> entirety, and if it contains pictures ,etc, it can become huge.
> 2. the object becomes "closed", in that it cannot be modified or checked in
> situ
> 3. it cannot be searched , without de-serialization.
>
>
> I'm looking to implement a java front end, (oracle back end), system ,that
> allows a product , to be inspected by an inspection team , and comments/
> photographic record kept.
>
> using an "object approach" would make it very simple, but the size of the
> resulting object could be very large.
>
> does anyone have any thoughts how to accomplish this task.

As you said above. If you have a proper data model, it should be a piece of cake. :)

-- 
-------------
- ByteCoder -           ...I see stupid people
-------------
                    Curiosity *Skilled* the cat
Received on Fri Dec 31 2004 - 03:45:20 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US