Back to the month index |
Back to the list index
|
Gary Bickford (garyb@outlawnet.com)
Tue, 14 Jan 1997 09:22:26 -0800
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Paulo Parola: "[mSQL] Forms processing"
- Previous message: Gary Bickford: "Re: [mSQL] 2.0 - can it cache results?"
- Maybe in reply to: Fernando Lozano: "[mSQL] 2.0 - can it cache results?"
- Next in thread: Ross Mack: "Re: [mSQL] 2.0 - can it cache results?"
Message-Id: <v01540b01af016f2ce35f@[208.192.38.113]> Date: Tue, 14 Jan 1997 09:22:26 -0800 From: garyb@outlawnet.com (Gary Bickford) Subject: Re: [mSQL] 2.0 - can it cache results?>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.
Yup. Especially as this is probably the easiest from Bambi's point of view
- just create it, if possible, return and go on. No worries.
end
=======
Gary Bickford, FXT Corporation http://www.fxt.com
System integration, active web site design, intranets.
garyb@fxt.com 541-923-3060
--------------------------------------------------------------------------
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: Paulo Parola: "[mSQL] Forms processing"
- Previous message: Gary Bickford: "Re: [mSQL] 2.0 - can it cache results?"
- Maybe in reply to: Fernando Lozano: "[mSQL] 2.0 - can it cache results?"
- Next in thread: Ross Mack: "Re: [mSQL] 2.0 - can it cache results?"