Re: BOM application

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Sat, 23 Nov 2002 16:31:34 -0000
Message-ID: <arobtl$cj8$2$8300dec7@news.demon.co.uk>

Object types will almost certainly make things more complicated in the database - although you might use memory variables of object types and then unpack them into relational tables.

Look at the CONNECT BY query - it is more or less designed for BOM reporting.

Sequence is probably better than sys_guid() - but I tend to prefer meaningful keys to synthetic ones.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____England______January 21/23


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html





John wrote in message ...


>Hi, gurus

>Data of engineering Bill Of Materials  are very hierarchical, nested,

and


>complicated.

>I'd appreciate your comments on followings:

>

>(1) Will Object-Relational features of Oracle (VARRAY, NESTED TABLE,

...) be


>a help?

>     Or, will those features make things more complicated?

>      What about querying complexity and performance of those

features?


>

>(2) Are there any tools that allow designers and developers of

relational


>    DBMS for developing hierarchical data application (complicated,

nested


>data, e.g., BOM)

>

>(3) sys_guid()? or sequence? for primary keys

>    Which should I use and when? Any pros and cons?

>

>Much thanks in advance,

>--

>John

>

>

>

>

Received on Sat Nov 23 2002 - 10:31:34 CST