My current understanding of the delta between Views and Temporary Tables Views are read only results from 1 or more tables ..in Oracle they are stored in TEMP tablespace http://www.psoug.org/reference/views.html
Temporary Tables are tables which are created/updated/inserted and exist only for the duration of your client session Oracle calls these Global Temporary Tables http://www.psoug.org/reference/gtt.html HTH Martin ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. > From: st...@ibushost.com > To: ba...@xaprb.com > CC: mysql@lists.mysql.com > Subject: RE: MySQL View > Date: Mon, 9 Feb 2009 10:10:45 -0600 > > > > > -----Original Message----- > > From: baron.schwa...@gmail.com [mailto:baron.schwa...@gmail.com] On > > Behalf Of Baron Schwartz > > Sent: Monday, February 09, 2009 9:19 AM > > To: Steven Buehler > > Cc: mysql@lists.mysql.com > > Subject: Re: MySQL View > > > > On Mon, Feb 9, 2009 at 9:41 AM, Steven Buehler <st...@ibushost.com> > > wrote: > > > Ok, I just saw a post about using view's in mysql. I tried to look > > it up > > > and found how to use it, but my question is: what is a view and why > > would > > > you use it? Is it like a temporary table? Does it write a new > > database to > > > the disk or use memory? > > > > A view is a piece of SQL whose result can be queried like a table. It > > stores no data; the results are always generated as the query > > executes. In some cases it does use a temporary table to hold the > > result and then query against it; in other cases it merges the > > original query's SQL and the view's SQL together and then executes the > > resulting query. > > > > Why use it? To abstract a complex bit of code away for simplicity. > > To grant permissions in a certain way (you can grant access to the > > view and deny access to the underlying table). > > > > There's a lot of complexity to it though, in terms of how to use views > > correctly and get good performance. I think the manual goes over it > > in good detail, and our book High Performance MySQL 2nd Edition has > > probably the best exploration of it otherwise. > > > > Baron > > Baron, Thank You > Questions: > 1. The view is temporary then? So it kind of uses it "in place of" a > temporary table? > 2. Does it go away after the query or after the mysql_close? > > I am going to have to go to the book store and get your book too. > > Thanks > Steve > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=mgai...@hotmail.com > _________________________________________________________________ Windows Live™: Keep your life in sync. http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t1_allup_howitworks_022009
