Thanks for you responses! This list has proven to be for useful to pick
pick the brains of other DBA's.
I think we are probably going to go the route of splitting the different
pieces of data into seperate columns, while keeping the original product_id,
since we have a lot of third party applicat
Rod Heyd wrote:
Hi Everyone,
I've got a little debate that maybe you can all help me settle.
I have three tables that I need to join, but there are performance problems
with the joins due to some misunderstandings of my predecessor about what's
needed to join the tables efficiently.
Here's the
Rod Heyd <[EMAIL PROTECTED]> wrote on 12/09/2005 11:01:38 AM:
> Hi Everyone,
>
> I've got a little debate that maybe you can all help me settle.
>
> I have three tables that I need to join, but there are performance
problems
> with the joins due to some misunderstandings of my predecessor about
CTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, October 21, 2002 9:17 PM
Subject: RE: normalization question
Hi!
I don't understand problem. Car can belong to only one Dealer, and one
Dealer can have many Cars, therefore DealerID should be in Car table. Also
Car can
Hi!
I don't understand problem. Car can belong to only one Dealer, and one Dealer can have
many Cars, therefore DealerID should be in Car table. Also Car can be only one Model,
but there are many Cars the same Model. It looks quite normal to put ModelID into Car
table, and I don't see any possib
June 04, 2002 6:38 PM
To: [EMAIL PROTECTED]
Subject: RE: Normalization question
I have a question about the setup of the tables in my database.
In my members table, I store a lot of info about demographics, such as
marital status, income, etc. The way I'm doing this is the enum type. Is
it bett
t;correct" way to do this?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 04, 2002 6:24 PM
To: Daren Cotter
Subject: Re: Normalization question
Your message cannot be posted because it appears to be either spam or
simply off topic to
l [mailto:[EMAIL PROTECTED]]
>Sent: Sunday, August 19, 2001 7:34 AM
>To: Daren Cotter
>Cc: [EMAIL PROTECTED]
>Subject: Re: normalization question
>
>
>
>Hi Daren,
>
>How long do you need to store this information? The normalized table
>that you describe is simple and e
aren Cotter
CEO, InboxDollars.com
http://www.inboxdollars.com
(507) 382-0435
-Original Message-
From: Rene Churchill [mailto:[EMAIL PROTECTED]]
Sent: Sunday, August 19, 2001 7:34 AM
To: Daren Cotter
Cc: [EMAIL PROTECTED]
Subject: Re: normalization question
Hi Daren,
How long do you need to store t
Hi Daren,
How long do you need to store this information? The normalized table
that you describe is simple and easy to index. Having several million
rows in the table won't bother MySQL. So is it sufficient to keep the
data around for a month and then prune it out of the database? Long
term
10 matches
Mail list logo
