On 5/17/05, Jigal van Hemert <[EMAIL PROTECTED]> wrote:
> From: "Rod Heyd"
> > Tables Version_(1-5)
> >
> > --
>
> > ID |PRODUCT_ID |DATA1 |DATA2 |DATA3 |.|DATA_N |
> > -
You should have a compound index in all your tables on ID+PRODUCT_ID,
since that is what you are joining on. Ideally, you should also have an
index on the DATA column that you will be using in the WHERE clause.
But your structure does really lend itself to this.
Going forward, you may think
From: "Rod Heyd"
> Tables Version_(1-5)
>
> --
> ID |PRODUCT_ID |DATA1 |DATA2 |DATA3 |.|DATA_N |
> --
I have a question about joins. My situation is as follows:
I have 5 tables identical in structure. Each table represents essentially
the same data, however, the data in each table represents a different
"version." The processing involved in generating the values stored in each
table may have ch
On Sun, Nov 04, 2001 at 01:06:27AM +0100, florian wrote:
>
> im storing pretty big amounts of customer data in a mysql databases.
> its about 2 million rows. what im wondering about now is, how does
> mysql perform joins on such amounts of data?
>
> i was planning to split the info in at least 3
well. for now it can only be one contact and one address per
customer. the thing
is though, that also other people can have addresses and contacts. so
for example
there will be a user table or something like that. and a user will also have
address and contact information.
would you still rec
Well, you usualy split your data in tables for a reason, because some data in
mulitple numbers are associated to one, or multiple data.
In your case, if you have one address and contact per customers, then make it
one table.
If you have an unknown numer of contacts and numbers per customer, the
hello!
im storing pretty big amounts of customer data in a mysql databases.
its about 2 million rows. what im wondering about now is, how does mysql
perform joins on such amounts of data?
i was planning to split the info in at least 3 tables: a general
customer table,
a address table, and a co
