View Support using Virtual Tables in Gupta's SQLWINDOWS ?

While browsing through SQLWINDOWS - SQLTALK manual I came across following

SET FETCHTHROUGH ..... If OFF - SQLBASE fetches from client's input message buffer.

         ON - fetches data from backend ensuring uptodate data.

If result set was created by a select command that contains DISTINCT,GROUP BY, HAVING,UNION ... ...or complex view then SQLBASE creates a virtual table. In these cases if you update in this situation and later fetch an updated row, the row will NOT reflect update even if Fetchthrough is ON.

Question 1. Does this mean that I get outdated data even if another user has

             long commited it , because my view was complex or involved HAVING ? Question 2. What is the way to always get current data however complex the view

             may be ?
Question 3. Is this normal behaviour ? I know that if one sets 'transaction

	     readonly ' then even oracle will not reflect updates of someone
	     else (it is like a snapshot of data). Oracle also does not create
	     virtual table and executes view at run time. what about SYBASE ?

Aniruddha Kortikar (kortikar_at_mipos2.intel.com)

E-mail 	: kortikar_at_mipos2.intel.com | A billion here, a billion there ...
Phone(W): 408 765 5515              | pretty soon it adds upto real money.


-------------------------------------------------------------------------------