I am sorry if i wasn't clear with my problem the first time.
My problem isn't file system and the way i lay it out.
What i need to know is a way to stream out external resource files via stored procedure calls.
Steps:
(1) User calls stored procedure ReadImage(ImageID).
(2) Stored procedure reads the Image table to find the location (field) for the given ID.
(3) Now this stored procedure ("HOW TO?") opens the file.
(4) Then it "Streams" it out to the User (as if it was a BLOB).
(5) For User its just like a lo_export but he has no clue if its stored in database or a seperate resource file system.
Resource file system can be accessed only through the database, where we will check for permissions if we need to (though i know i can implement permissions in the file systems as well).
What is the best way to do Steps (3) and (4) above?
thanks,
vish
(vishal saberwal)
On 11/4/05, Douglas McNaught <doug@xxxxxxxxxxxx> wrote:
vishal saberwal <vishalsaberwal@xxxxxxxxx> writes:
> HFS is the filesystem richard was tlking about. I am not familiar with
> this file system but i guessed it was HFS+ that he was talking about.
> yes, i understand all modern filesystems are Hirearchical file systems.
Oh, OK--reading your original message, you just want to store the data
files in a hierarchical arrangement of some sort.
-Doug
