From: Bernard Peek Subject: Re: What DB to use for lots of IMAGE files? Date: 1997/05/05 Message-ID: #1/1 Distribution: world X-NNTP-Posting-Host: intersec.demon.co.uk References: <336D556B.967@wohl.slh.wisc.edu> <336dda6c.17216435@gate.idg.no> Organization: Yoyodyne (UK) Newsgroups: comp.databases.rdb,comp.databases.informix,comp.databases.oracle.server,comp.databases.ingres,comp.databases.gupta,comp.databases.ibm-db2,comp.databases.ms-access,comp.databases.ms-sqlserver,comp.database.paradox,comp.databases.sybase,comp.databases.theory,comp.databases.visual-dbase In comp.databases.theory, article <336dda6c.17216435@gate.idg.no>, Nils Myklebust writes > >Mirwais Qader wrote: > >:What format should the image data be stored in (.jpg, .gif, .tif, >:....)? > >The format your application can most easily handle. >These databases store data in BLOBs and doesn't care about the format. If there is a large amount of data in bitmap images there are some difficult decisions to be made. To minimise the storage requirements you might choose one of the "lossy" compression methods, like JPG. You then have a tradeoff between storage size and image quality. If you are storing medical images then your users may require you to choose a lossless method. Talk to your users. Find out what they need the system to do. Then find out what they *want* the system to do. Learn to tell the difference between the two types of request. -- Bernard Peek bap@intersec.demon.co.uk