Mailing List Archive


Back to the month index Back to the list index
Ross Mack (rossmack@gui.com.au)
Wed, 15 Jan 1997 13:46:38 +1100 

Message-Id: <199701150246.NAA27624@budgie.gui.com.au>
From: "Ross Mack" <rossmack@gui.com.au>
Subject: Re: [mSQL] 2.0 - can it cache results?
Date: Wed, 15 Jan 1997 13:46:38 +1100

>
> But then that gives the worst of both worlds. The applications have to
> work out a way to try to generate a unique name for the table (as there
> may be many people running the same query at the same time). You can't
> just chuck a PID on the end as the app's could be running on various
> machines client/server.
Hang on, if the table already exists because someone else is using the same
query then why not just use it ? At worst check the datetime it was created
and decide whether or not it's too old. If it is then you need to wait for
locks on that table to be released and then create your own version.
I guess the thing is that this is a problem for all client server work and
it really depends on how your data works as to what is good for your app.
If this si going to be a serious problem then maybe you need to revise your
data structure to something more flexible that doesn't require temporary
tables all over the place.
I would think the requirement for such items would be extremely limited in
web development anyway. Unless you can create, query and destroy such a
table in a sufficiently small time to create and return a page then they
are of no use anyway. However, a SELECT INTO implementation is of use
ANYWAY in web development or outside.
I've just noticed another reply from rasmus so I will cut this one short
here.
        - Ross
--------------------------------------------------------------------------
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!