Mailing List Archive


Back to the month index Back to the list index
Fernando Lozano (bl@riosoft.softex.br)
Wed, 08 Jan 1997 09:39:45 -0800 

Message-Id: <32D3DBE1.3561@riosoft.softex.br>
Date: Wed, 08 Jan 1997 09:39:45 -0800
From: Fernando Lozano <bl@riosoft.softex.br>
Subject: [mSQL] Re: 2.0 - can it cache results?

Hi, Ramsus!

> > The logical way to do this is to link the tmp table to the session handle
> > in msql2d.
>
> Linking it to the session handle would sort of defeat the purpose. Could you
> not create a unique identifier of some sort which map to the new table?
>
> . The unique identifier should not be a normal valid table name, or it
> should be so long and cryptic that it has an extremely high probability
> of never interfering.

Some comercial database servers use a fist character that is not allowed
in an create table statement, but is accepted by select statement. MS
SQL Server, for example, uses an "#", and uses an "##" for a temp table
that will be visible by another app (with the name specified in
select..into)

> . When should the temp table be deleted? I would prefer if it were left
> up to the client application to delete it, but it would be neat if
> it could be given a timeout.

All databases I know delete temp tables when the connection ends, and I
think this is the better approach.

> . I don't think these tables should show up in an msqldump, nor should they
> survive if msqld is stopped and restarted. They should survive a reload
> though.

That looks fine to me.

[]s, Fernando Lozano
--------------------------------------------------------------------------
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!