Back to the month index |
Back to the list index
|
David J. Hughes (bambi@Hughes.com.au)
Wed, 15 Jan 1997 18:09:25 +1000 (EST)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Eric Huss: "Re: [mSQL] Can 1.0.16 do this?"
- Previous message: David J. Hughes: "Re: [mSQL] Can 1.0.16 do this?"
- In reply to: Kerry Garrison: "[mSQL] Can 1.0.16 do this?"
- Next in thread: Ross Mack: "Re: [mSQL] 2.0 - can it cache results?"
Date: Wed, 15 Jan 1997 18:09:25 +1000 (EST) From: "David J. Hughes" <bambi@Hughes.com.au> Subject: Re: [mSQL] 2.0 - can it cache results? Message-Id: <Pine.SUN.3.91.970115180521.21123Q-100000@webster.AusWeb.com.au>
On Wed, 15 Jan 1997, Ross Mack wrote:
> Hang on, if the table already exists because someone else is using the same
> query then why not just use it ?
How about
select * from dept into dept_result where dept=SomeDepartment
The user could specify the department as part of the application process
and trigger the same query with the new dept name. So, the table exists
but is filled with data that's not correct for the secod query that's
sent along.
I agree with your point before that at some point in time the programmer
must be responsible for his own actions. I also know how much e-mail I
get with so-called "silly" questions. From my point of view, if it is
easy for a user to create solid applications (i.e. ones that don't fill
the disk up with tmp table because they for got to drop it etc) then
that's best. If I can also do that in a way that is still very handy for
the hard-core DB guys then that's even better.
Like I said, let me have a think about it.
Bambi
...
--------------------------------------------------------------------------
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: Eric Huss: "Re: [mSQL] Can 1.0.16 do this?"
- Previous message: David J. Hughes: "Re: [mSQL] Can 1.0.16 do this?"
- In reply to: Kerry Garrison: "[mSQL] Can 1.0.16 do this?"
- Next in thread: Ross Mack: "Re: [mSQL] 2.0 - can it cache results?"