There was a topic about this issue couple of days ago... I'll just paste
the answer of Bob (nice one by the way!)...Hi folks, when you think about what the job of an operating system is, you'll find he solution why database-stored data (Data, names blobs, anything) CAN (not must) be retrieved faster than to access a file in the system's (hirachical!!!) file structure. The first reason is this Tree-oriented thing for a directory The second is: a database is optimized for fast data finding (that's where keys are for) the os relays more on sequencial searching and just caching some hundred entries(which is quite a lot in terms of a human user!). The last MIGHT be some extra-added break as an anti-virus-software which at least has to check whether to scan that file or not. If you happen to have a directory with a couple of thousand files, youz'll see, how long it takes to open that dir in the explorer. That's rather long compared to showing the records of a db in a grid, even if there are some thousands. Now, with that knowlege that a DB might be better how to proceed, where are the pitfalls The database file(s) whichever you use tend to become bigger and bigger. Handling of big files (backup, move copy) becomes harder with increasing dimensions. and the danger of corruption grows with the filesize. What leads out of that? Divide an conquer! DBs are (mostly) able of beeing spread over several files. (Interbase/firebird at least is) You could as well spread your Files into a hundred sub-Directories having not more than 1000 files in a dir which does not slow down the os too much. and having the file-paths stored in the db. This would have the advantage of accessing the files witout using the database (if you know the name of the file) So it stays the same all over: it's up to you to decide what2do! make up a list of goodies and not so goody for your choices and let your customer decide whith what he'll live. Have fun! Bob -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Jason Fischer Sent: Friday, April 22, 2005 8:41 AM To: [email protected] Subject: [delphi-en] Saving images - bit off topic Hi all, This is bit off topic, but some suggestions would be great. Is it a good idea to store images in an access db. Or should I rather just store the file path to the image? Keep in mind that there could be a lot of images that might be stored so I am looking for an all round solution. Thanks ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] ---------------------------------------------------------------------------- ---- Yahoo! Groups Links a.. To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ b.. To unsubscribe from this group, send an email to: [EMAIL PROTECTED] c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. [Non-text portions of this message have been removed] ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
