Back to the month index |
Back to the list index
|
Owen Scott Medd (osm@interguide.com)
Tue, 14 Jan 1997 12:07:52 -0500 (EST)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Gary Bickford: "Re: [mSQL] 2.0 - can it cache results?"
- Previous message: Shane Caraveo: "Re: [mSQL] Windows95 port"
- In reply to: Peter Tillemans: "Re: [mSQL] Windows95 port"
Date: Tue, 14 Jan 1997 12:07:52 -0500 (EST) From: Owen Scott Medd <osm@interguide.com> Subject: Re: [mSQL] 2.0 - can it cache results? Message-Id: <Pine.LNX.3.95.970114120352.15180C-100000@home.interguide.com>On Tue, 14 Jan 1997, David J. Hughes wrote:
> 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).
What would be wrong with implementing the ansi sql 'into' functionality,
but then also implementing a new table attribute for specifying table
expiration date? I haven't seen any suggestions yet that really deal well
with the web paradigm, but adding the extension of limited lifetime tables
(with the ability to extend their lifetimes by moving their expiration
point forward), would seem to be useful for this application.
Owen
-- USMail: InterGuide Communications, 200 Orchard Hills Dr, Ann Arbor, MI 48104 Phone: +1 313 213-9030 FAX: +1 313 213-9011 Internet: osm@interguide.com WWW: http://www.interguide.com/~osm/[ This is an uncontrolled document. ]
-------------------------------------------------------------------------- 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!
- Next message: Gary Bickford: "Re: [mSQL] 2.0 - can it cache results?"
- Previous message: Shane Caraveo: "Re: [mSQL] Windows95 port"
- In reply to: Peter Tillemans: "Re: [mSQL] Windows95 port"