• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Store (large) images inside or outside database?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Store (large) images inside or outside database?


  • Subject: Re: Store (large) images inside or outside database?
  • From: email@hidden
  • Date: Fri, 8 Feb 2008 11:22:47 +0100

Hi,
as far as I remember, oracle 9i uses to store big blobs in the filesystem and handles them with an internal link - I suppose this to be the default, though you can make the db store everything within its own files. So I would prefer the option of pushing all images into the fs and handle them as references within the db. Don't forget to add fs-backups for the image-area corresponding to your backup strategy and configure both properly within oracles backup manager.
Generally we handle all of our (sometimes even bigger) images and image bundles on the filesystem and give the db a link to them.


Hth

sip

Am 08.02.2008 um 10:58 schrieb Susanne Schneider:

Hi everyone,

<seems that all have moved to the apple-list, so I repost my message here. Jerry, in any case thanks for the link.>

today I need some advice on a conceptual basis:
We need to include images in our WO 5.2.3 application working
with Oracle 9.i as a database. The images may be of various kind
including DICOM images and therefore could be very different in size
(maybe from 100 KB up to 100 MB or even more).

Besides the problem of handling such variety of formats I could not
really make up my mind if we should store such large objects in the
database and reflect them with eo-properties or store them in the
filesystem and only the pointer in the database. The images are treated
as read only: once they were uploaded they will be stored and only be
displayed for download/view. The image property would be put into a
separate table to be only loaded if needed. It is not possible to put the images under webserver-control because they include sensitive information.


These were my considerations:
- memory consumption while using eos (as I understood the image- property
would at least be hold twice: once in the eo in every editing context
and once in the snapshot)
- backup and recovery issues of the database
- transaction management


Any comments?
Susanne
--
Susanne Schneider
Coordinator secuSuite Development

iAS interActive Systems GmbH
Dieffenbachstraße 33 c, D-10967 Berlin

fon    +49(0)30 69 00 42 - 05
fax    +49(0)30 69 00 42 - 10
mail   email@hidden
web    http://www.interActive-Systems.de

----------------------------------------------------
Geschäftsführer: Dr. Marko Reschke, Thomas Fritzsche
Sitz der Gesellschaft: Berlin
Amtsgericht Berlin Charlottenburg, HRB 106103B
----------------------------------------------------

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Store (large) images inside or outside database? (From: Susanne Schneider <email@hidden>)

  • Prev by Date: Store (large) images inside or outside database?
  • Next by Date: Re: Eclipse Default Template Issue?
  • Previous by thread: Store (large) images inside or outside database?
  • Next by thread: Re: Store (large) images inside or outside database?
  • Index(es):
    • Date
    • Thread