Back to the month index |
Back to the list index
|
Jason Bodnar (jcbodnar@mail.utexas.edu)
Tue, 07 Jan 1997 11:31:03 -0500
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Gary Bickford: "Re: [mSQL] 2.0 - can it cache results?"
- Previous message: Ralf Laemmel: "[mSQL] How to test w3-msql"
- Next in thread: Gary Bickford: "Re: [mSQL] 2.0 - can it cache results?"
Message-Id: <1.5.4.32.19970107163103.0068c37c@mail.utexas.edu> Date: Tue, 07 Jan 1997 11:31:03 -0500 From: Jason Bodnar <jcbodnar@mail.utexas.edu> Subject: Re: [mSQL] 2.0 - can it cache results?At 10:33 AM 1/7/97 -0500, you wrote:
>Some issues:
>
> . 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.
Unique temp table names are necessary but perhaps there's an easier way to
implement this. Maybe normal tables should be restricted to starting with an
alphanumeric character. Then you could start temp tables with a
non-alphanumeric character.
Just a thought. I'm trying to remember how some of the other dbs I've used
do this (namely Informix).
Jason Bodnar
Internet Programmer
Cox Interactive Media
jasonb@onr.com
--------------------------------------------------------------------------
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: Gary Bickford: "Re: [mSQL] 2.0 - can it cache results?"
- Previous message: Ralf Laemmel: "[mSQL] How to test w3-msql"
- Next in thread: Gary Bickford: "Re: [mSQL] 2.0 - can it cache results?"