Totally depends on the data in question. I tend to organise my data in a mySQL database, for easy queries, sorting, categorisation, etc etc. However sometimes I associate a file to a record (eg a photo of a member or employee)... so the employee with the id 45 will have a photo stored in the filesystem called 45.jpg.
I tend to keep raw-text-based data in a database, and binary or heavily formatted data (mp3s, giffs, JPEGs, PNGs, .doc's, .xls's) in the file system, attached to the database records. I've read that you get faster queries by separating bulky data from the simple stuff... this separation can be done with files, or with relational db tables... I guess it depends a lot on what sort of data, how you will use it, and which your prefer (file/db). One other bit of advice i've read: if you do have LOTS of files in a filesystem (1000's, not 100's), it's best to break them up somehow... by alphabet (a/, b/, c/, etc), year (2002/, 2003/, 2004/, etc), category (entrés/, mains/, soups/, deserts/, etc), etc. on 09/01/03 4:04 PM, Erich Kolb ([EMAIL PROTECTED]) wrote: > I am going to be dealing with a ton of data shortly and my goal is to make > it accessible via the web. I am curious about the performance differences > between using a database or leaving the data in the individual files they > originated in. Can anyone offer any recommendations? Justin French -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
