Depends on in which manner you are going to be using the dB I'd suggest, i.e. just for storage for the arrays or querying the data while it is in the dB.
If the data is all related and you are going to be running queries across the whole data set I'd put it all in one table, if the quires that you are running are specific that you can narrow it down to a table (i.e. design it so that the application accessing the dB knows what table to go for) do that, because then the isolation would provided better management. Personally I'd use different tables, but the amount of data is no where near an issue, I run a app against mysql that has arrays around 250-300K at the moment and its fine. Jerry ----- Original Message ----- From: "gregory lefebvre" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 24, 2003 3:07 PM Subject: Large table or several tables ? > Hye the list, > > There is my problem. > > I have to register about 400 large arrays (~10000 lines each) in my > MySQL database and I don't know which of the following choices is better. > Either create a large tables as a stack, which contains all arrays > Either create as many tables as there are arrays and use references to > each table. > > Any advice is welcome. > Thank you very much > > Greg > > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
