|
I have an application that will
require access to app. 1000 photos (could grow to 4000-5000) currently stored
in JPEG format and app.400 Kb in size (each). The options are: - Store the pictures in a separate
directory and have a table in the database that stores the filename and path
and when the photo needs to be displayed, it simply “launches” the photo using
a an external viewing software (such as photo editor) - Load the picture as a blob, store
it in the database and display it from (or within) a form. - Store the photos in a separate
database, attach it to the main database for access and display. What is the compression/overhead when
storing pictures as blobs? The database is currently app. 60 Mb and it would grow
considerably if the photos are stored in the database. What would be the
performance penalty? Any thought on these approaches or
any other that some one has successfully used would be greatly appreciated. Javier Valencia,
PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln., Suite #14 Olathe, KS
66062-4571 (913)829-0888 (913)649-2904 FAX |
- RE: Storing pictures Javier Valencia
- RE: Storing pictures Bill Eyring
- Re: Storing pictures - Razzak's Reply A. Razzak Memon
- Re: Storing pictures Lawrence Lustig
- RE: Storing pictures Betaserver
- RE: Storing pictures Troy Sosamon
