Mailing List Archive


Back to the month index Back to the list index
rasmus@mail1.bellglobal.com
Tue, 14 Jan 1997 09:57:12 -0500 (EST) 

From: rasmus@mail1.bellglobal.com
Date: Tue, 14 Jan 1997 09:57:12 -0500 (EST)
Subject: Re: [mSQL] 2.0 - can it cache results?
Message-Id: <ML-2.3.853253832.2160.rasmus@inet-dev>

> The problem with this is that these tables a temporary but there is no
> mechanism to enforce that status. The "tagging" convention I mentioned
> in my original message handles this temporary nature as ther server can
> tell when they are no longer required (in the usual client'server
> application sheme of things). The problem is caused by the
> connectionless nature of the web in that there's no way of knowing when
> the client is through so the client is forced to manually remove the tmp
> table (bad plan if you don't have more spare disk space than last year's
> production from the Seagate factory).

Then I think the best idea is to forget about the idea of temporary tables.
Implement the real ANSI "select into" clause and let the client-side worry
about dropping tables that may no longer be needed.

-Rasmus
--------------------------------------------------------------------------
To remove yourself from the Mini SQL mailing list send a message containing
"unsubscribe" to "unsubscribe" to msql-list-request@bunyip.com. Send a message containing
"info msql-list" to majordomo@bunyip.com for info on monthly archives of
the list. For more help, mail owner-msql-list@bunyip.com NOT the msql-list!