On Wed, 2007-07-04 at 22:27 +0100, Gregory Stark wrote: > "Pavel Stehule" <[EMAIL PROTECTED]> writes:
> > Catalog bloat is one unwanted effect. Second is different behave of > > temp tables than other mayor rdbms, and uncomfortable work with temp > > tables in stored procedures. Third argument for implementation of > > global temp tables is full support of ANSI SQL, > > I think the ANSI concept of temporary tables which are defined once but give > you a fresh empty work-space for each transaction only makes sense if you're > thinking in terms of an OLTP environment. Otherwise you would just go ahead > and do the DDL to create new tables for each query and not worry about the > down-sides. > > The advantages of the ANSI temporary tables are all things you would worry > about in an OLTP environment but not a data warehousing environment: IIRC there were similar problems with temp table usage at many DW sites using Teradata. The issue was about locking, specifically the access rights required. We might have that problem, or not, but the issues related to significant numbers of temp tables effect many types of application., not just OLTP. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
