Amir Hardon wrote:
For example what will be better, storing all items information in one table
with one column for category, or having a separate items table for each
category.
My guess is that separate tables will be faster for use but will consume more
disk space.
It's a good example where
Yedidyah Bar-David wrote:
No it's not.
What you can do is called a subquery. That is, do a 'select' on the
output of another select, interpreted as data, not as a table name.
Look carefully at the mentioned URL.
There are no subqueries in MySQL 3.x and 4.0.x, only 4.1.x onwards.
However, it is poss
No it's not.
What you can do is called a subquery. That is, do a 'select' on the
output of another select, interpreted as data, not as a table name.
Look carefully at the mentioned URL.
--
Didi
> On Wednesday 09 June 2004 21:40, Shlomi Fish wrote:
> > On Wednesday 09 June 2004 16:50, Amir Hardon
On Wednesday 09 June 2004 21:40, Shlomi Fish wrote:
> On Wednesday 09 June 2004 16:50, Amir Hardon wrote:
> > Hi,
> > I'm planning a DB structure for an e-commerce system, and facing some
> > question about the DB efficiency that I don't know how to approach.
> >
> > For example what will be better
On Wednesday 09 June 2004 16:50, Amir Hardon wrote:
> Hi,
> I'm planning a DB structure for an e-commerce system, and facing some
> question about the DB efficiency that I don't know how to approach.
>
> For example what will be better, storing all items information in one table
> with one column f
On Wed, 9 Jun 2004, Amir Hardon wrote:
> Hi,
> I'm planning a DB structure for an e-commerce system, and facing some question
> about the DB efficiency that I don't know how to approach.
>
> For example what will be better, storing all items information in one table
> with one column for category,
One possible approach:
Try both designs, fill them with lots of test data and benchmark the
performance.
Also use EXPLAIN SELECT (a MySQL command which gives you information
about how it is going to execute the actual SELECT command).
I read about this stuff in MySQL Reference Manual, published
Hi,
I'm planning a DB structure for an e-commerce system, and facing some question
about the DB efficiency that I don't know how to approach.
For example what will be better, storing all items information in one table
with one column for category, or having a separate items table for each
categ
