Back to the month index |
Back to the list index
|
Fernando Lozano (bl@riosoft.softex.br)
Thu, 09 Jan 1997 09:26:54 -0800
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Tim Weilkiens: "[mSQL] Connection refused on localhost"
- Previous message: Wolfy Su: "[mSQL] patch for some bugs...."
- Maybe reply: Fernando Lozano: "Re: [mSQL] Re: 2.0 - can it cache results?"
- Maybe reply: Mark H. James: "Re: [mSQL] Re: 2.0 - can it cache results?"
Message-Id: <32D52A5E.1105@riosoft.softex.br> Date: Thu, 09 Jan 1997 09:26:54 -0800 From: Fernando Lozano <bl@riosoft.softex.br> Subject: [mSQL] Re: 2.0 - can it cache results?Hi, Gary!
> >All databases I know delete temp tables when the connection ends, and I
> >think this is the better approach.
>
> As Rasmus pointed out, the connection ends when the web page ends, so in
> this application there would be no point in having temp tables unless they
> can persist.
I've missed the point thar he was interested in Web access...
> You bring up a good point though - how are the commercial dbms folks
> handling this in their new web server packages?
As far as I know they are using SELECT..INTO or big amoungs of RAM.
[]s, Fernando Lozano
Rio de Janeiro, Brasil
--------------------------------------------------------------------------
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: Tim Weilkiens: "[mSQL] Connection refused on localhost"
- Previous message: Wolfy Su: "[mSQL] patch for some bugs...."
- Maybe reply: Fernando Lozano: "Re: [mSQL] Re: 2.0 - can it cache results?"
- Maybe reply: Mark H. James: "Re: [mSQL] Re: 2.0 - can it cache results?"