Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!bbn!rochester!PT.CS.CMU.EDU!cadre!pitt!cisunx!mike
From: mike@cisunx.UUCP (Mike  Elliot)
Newsgroups: comp.databases
Subject: Re: Follow-up to: Problems with Unify
Message-ID: <7553@cisunx.UUCP>
Date: 7 Mar 88 18:38:15 GMT
References: <249@tsc3b21.UUCP> <50500005@upba> <350@vsi.UUCP>
Reply-To: mike@unix.cis.pittsburgh.edu.UUCP (Mike  Elliot)
Organization: Univ. of Pittsburgh, Comp & Info Sys
Lines: 24

In article <350@vsi.UUCP> friedl@vsi.UUCP (Stephen J. Friedl) writes:
>To make this easier, copy SQL to another name, say USQL.  Then
>run some kind of binary editor on it to change file.db[r] to
>File.db[r] (note capital 'F').  Then link unify.db to File.db
>and File.dbr and run USQL on the database.  The above warning
>is relevant but possibly less dangerous than constantly changing
>and relinking your database name from unify.db to file.db and
>back again.  Do you think Unify Corp. approves of this? many :-)
>-- 

I've called Unify phone support and they have had me do things like that.
Except they don't have you `mv' files around. You create a new directory
and do your links from there.

			Mike Elliot
			{allegra|bellcore|cadre|psuvax1}!pitt!cisunx!mike
			mike@pittvms.bitnet

It must be remembered that there is nothing more difficult to plan, more
doubtful of success, nor more dangerous to manage, than the creation of a
new system.  For the initiator has the enmity of all who would profit by
the preservation of the old institutions and merely lukewarm defenders in
those who would gain by the new ones.
			-Machiavelli