Re: Workspace Manager question

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Wed, 02 Feb 2005 19:45:05 -0800
Message-ID: <1107402144.311157@yasure>

GreyBeard wrote:

> On Wed, 02 Feb 2005 18:50:17 -0500, NowhereMan wrote:
>
>

>>Hello,
>>
>>I'm reading the "Oracle Workspace Manager Dev Guide", and came across this:
>>
>>"A workspace logically groups collections of
>>new row versions from one or more version-enabled tables, and isolates these
>>versions until they are explicitly merged with production data or discarded,
>>thus
>>providing maximum concurrency."
>>
>>Can someone help me understand how a workspace could have rows from more
>>than one table?  How would the workspace get populated?
>>
>>Thanks for any insight...

>
>
> Create a schema with one table, fire up Oracle Enterprise Manager 9i,
> create a workspace and enable the table in the workspace. Look at the
> resulting schema.
>
> You will find that the table gets replaced by a view that maps to the
> table. With the addition of a few columns and supporting info, you can
> now simulate a table that supports 'named versions' of rows. With a few
> added packages you can now simulate commits, rollbacks, etc. for
> transactions that persist across logoffs
>
> lol/FGB

Get out of EM and you'll find there are a few materialized views and other objects too. Creating a workspace creates a lot of objects.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)

Received on Wed Feb 02 2005 - 21:45:05 CST