Re: SQL question
- From: Jared Still <jkstill@xxxxxxxxx>
- To: Sandeep Dubey <dubey.sandeep@xxxxxxxxx>
- Date: Mon, 16 Jan 2006 16:49:13 -0800
Comments below:
On 1/16/06, Sandeep Dubey <dubey.sandeep@xxxxxxxxx> wrote:
>
>
> > On 1/13/06, Sandeep Dubey <dubey.sandeep@xxxxxxxxx> wrote:
> > > > I am sorry I can't be more helpful. I don't really see this as
> problem,
> > to
> > > > me it's more of an exemple of bad data.
> > >
> > > I am not sure if it is a bad data model. It's battle of normalization
> > > - denormalization.
> >
> > The example given would appear to be denormalized. There is no
> > candidate key to start with.
> >
> > > I have a table Items. It's child is item_parts. Item can be made up of
> > > 1 or may parts. So it is right to store in a table like item_parts.
> > > okay?
> >
> > The example does not match what you were trying to do.
> > You won't get much help here with an example like that.
> >
> > What you are trying to do requires 3 tables.
> >
> > ITEMS, PARTS, and an intersection table.
>
> The foo table in the example I gave is in fact item_part, child of
> item and part table. Item and part are many to many relationship. So I
> have table item_part (foo in this example) having column item and part
> ids. Sorry if I missed your point.
>
> --
Ah, so there are 3 tables.
I've found this thread rather confusing.
Perhaps if you post again with examples that are more clear
and representative of the problem you are trying solve, you would
get some helpful replies.
Including DDL and DML to create a test is a sure way to get
some respondents.
I know you did that in your original post, but it appears that that
example had little to do with the problem you are trying to solve.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Other related posts:
