Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
From: Michael Segel <msegel@segel.com>
Reply-To: msegel@segel.com
Organization: MSCC
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: Unable to create temporary table when using a readonly database
Date: Tue, 29 Nov 2005 16:17:26 -0600
User-Agent: KMail/1.8.2
References: <20051129181708.21336.qmail@web31902.mail.mud.yahoo.com>
 <200511291549.57500.msegel@segel.com> <438CCFE7.3030500@Sourcery.Org>
In-Reply-To: <438CCFE7.3030500@Sourcery.Org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200511291617.26478.msegel@segel.com>

On Tuesday 29 November 2005 16:02, Satheesh Bandaram wrote:
>  Michael Segel wrote:
>
>
>
> <>Eeewwww, apply the KISS rule. Where are the temp tables actually created?
>  In memory only? In /tmp? Or in some place where the JVM dictates? Or cwd?
>  (Current Working Directory).
>
>  If you had clicked on the second link I had, you would know the answer!
>
>
> For the read-only database, set the property derby.storage.tempDirectory to
> a writable location. Derby needs to write to temporary files for large
> sorts required by such SQL statements as ORDER BY, UNION, DISTINCT, and
> GROUP BY. For more information about this property, see Tuning Derby.
> derby.storage.tempDirectory=c:/temp/mytemp
What? 
Me read the manual? ;-)
Now that would take the fun out of it.

Again, that would allow Derby to function.
Why would you want to set up a read-only database where the app/user would 
also create temp tables? Kinda like letting people smoke in a non-smoking 
restaurant. ;-)

I really do think the better solution would be to create permissions and then 
allow the person to grant or revoke the permissions. But then again, that 
would be a major change...