>
> > > Modified Files:
> > > main.html
> > > Log Message:
> > > Add mention of TEMP tables.
> >
> > Bruce, would this be a good time to start the v6.5 release notes?
> > Certainly the temp tables capability would make the short list of
> > "highlighted features" in the 1-paragraph-per-topic summary above the
> > one-liners.
> >
> > Do you want to start the v6.5 section in release.sgml? Also, we
> > apparently have not yet gotten the v6.4.2 release notes in there either,
> > so perhaps you could drop those in also? I'll polish the markup as
> > needed...
> >
> > - Tom
> >
>
> OK, got to finish temp table and commit them first.
Don't know if you noticed my statement in another thread.
I think temp tables could confuse any function that uses the
prepared/saved plan feature of SPI manager. If such a
function called once saved a plan for a temp table named
'test', and later called again but 'test' is now another
table, probably the parsetree and plan might point to the old
(wrong, not anymore existent) table.
Should not be a real drawback against temp tables. But maybe
something to mention in the release notes.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck@debis.com (Jan Wieck) #