big table

[Ruslan Zasukhin]

On 6/4/04 7:57 PM, "olivier vidal" <vidal_olivier at yahoo.fr> wrote:

> Sorry to talk again of this problem but in my tests (with it is true
> few recordings), my database is faster (in reading) with a table of 150
> columns than with 10 tables of 15 columns. Join them are a little bit
> slow in that case.

Well, then go with 150 columns table!

It looks to me that you ALWAYS do join of 10 tables?

Just usually if you have 10 tables, you can for some task join only this 2-3
tables, for other tasks join that 2-3 tables...

 
>> I will not recommend to use with Valentina table with so many fields.
>> Because Valentina keep fields in separate files.
> 
> That is the risk of a big table (e.g. 150 columns)?
> A less stable database?

No of course

> slower savings and writing ?

Yes, Add/Delete can be slower.

> My customers will have approximately 500 to 5000 recordings in this big
> table.

Well, then this is not many.

You can make cache size 10-20 MB and all your data will be in cache.

> It is a POS software, there will be thus often small modifications in
> the table (e.g. in every sale, modification of the column 'stock' of
> every sold product).

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------