HP3000-L Archives

December 2000, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Donna Garverick <[log in to unmask]>
Reply To:
Donna Garverick <[log in to unmask]>
Date:
Mon, 4 Dec 2000 09:32:55 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
"Born, Ken" wrote:

> We are in the process of taking proposals for a new system.  One of the
> requirements is that the database must be able to store images(Mugshots).
> Can IMAGE store images in its database?  Are there any plans to?  Would I
> need to migrate over to ALLBASE?

well, yes and no.  image can't directly support blobs (unless they were
perhaps very small and you made the effort to put their contents into fixed
length records).  otoh, image can very nicely maintain a dataset that is a
simple list of file names that 'point' to external 'blob' files (think of
using hfs namespace!).  of course, the problem then is trying to maintain the
files -- since they're external to image (think of a broken 'pointer' (a
missing file)) -- and trying to enforce security (it's a different ball of
wax outside of the database).

i believe allbase could handle blobs (but don't take my word for it).  i
don't see that you'd need to convert the entire database to allbase though --
and given allbase's precarious state (imo), it certainly casts a shadow on
the 'using allbase' decision.

with some work (system design) i believe you can find a suitable solution --
but sadly i don't think it will be an 'off the shelf' sort of
answer.             - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

"Unix _is_ user friendly.
It's just very selective about who its friends are.
And sometimes even best friends have fights."

>>>MY opinions, not Longs Drug Stores'<<<

ATOM RSS1 RSS2