Re: Global temporary tables in Java DB -- Apache Derby
- From: Dyreatnews@xxxxxxx
- Date: Tue, 18 Dec 2007 17:21:10 +0100
CJ <spambox1@xxxxxxxxxxxxxx> writes:
[snip]
I have use SQL engines that use naming conventions such as
"#tableName" and "##tableName." In the former, one pound character (#)
the behavior is similar to the Derby declared global temporary table,
the latter, the double pound character (##) creates a temporary table
that is available to all within the scope of the schema.
IMHO, something labeled as "global" that restricts access to the
entity that created is not global in any definition I can imagine.
It may not seem reasonable, but that is what
ISO/IEC 9075-2:2003
Section 4.14.2
9th paragraph
states.
--
dt
Questions about Derby/Java DB? Please visit
http://db.apache.org/derby/derby_mail.html
.
- References:
- Global temporary tables in Java DB -- Apache Derby
- From: CJ
- Re: Global temporary tables in Java DB -- Apache Derby
- From: Dyreatnews
- Re: Global temporary tables in Java DB -- Apache Derby
- From: CJ
- Re: Global temporary tables in Java DB -- Apache Derby
- From: Dyreatnews
- Re: Global temporary tables in Java DB -- Apache Derby
- From: CJ
- Re: Global temporary tables in Java DB -- Apache Derby
- From: Dyreatnews
- Re: Global temporary tables in Java DB -- Apache Derby
- From: CJ
- Global temporary tables in Java DB -- Apache Derby
- Prev by Date: Openwave Hiring Indian Professional for H1B
- Next by Date: Beginner question about JDO best practice
- Previous by thread: Re: Global temporary tables in Java DB -- Apache Derby
- Next by thread: Yellowfin Business Intelligence Version 3.3 release
- Index(es):
Relevant Pages
|