Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!marque!gryphon!cadovax!erick
From: erick@cadovax.UUCP (Eric Kleinberg)
Newsgroups: comp.databases
Subject: Re: Modifying an SQL package to access proprietary file system.
Keywords: SQL
Message-ID: <2223@cadovax.UUCP>
Date: 29 Aug 88 02:17:14 GMT
References: <1398@ektools.UUCP> <1961@tekcae.CAX.TEK.COM> <3104@homxc.UUCP> <379@infmx.UUCP>
Reply-To: erick@cadovax.UUCP (Eric Kleinberg)
Organization: Contel Business Systems, Torrance, CA
Lines: 12


	Has anyone modified an SQL package to interface to a proprietary
file system? My idea is to buy an SQL package and remove the modules 
containing the I/O calls to the UNIX file system, replacing them with
calls to a proprietary file manager. Hopefully, this can be done without
buying source rights but instead an unlinked object library. I would
appreciate any insights into this (not whether it is desirable!). The
'typical' SQL package incorporates a file system with indexes stored as
B-Trees and records stored 'end-to-end'. I would keep the B-tree structure
but would replace the file in which the data record is stored. Since our
file system is rather 'unique', there would have to be conversion of 'fields'
from our format to the format expected by the SQL package.