Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Design question

Design question

From: Stephens, Chris <ChrisStephens_at_pqa.com>
Date: Fri, 22 Oct 2004 08:08:38 -0400
Message-ID: <0C36D9C74ADA844292F3218A9C6345442B944B@exchange.pqa.local>


=20

I've just been asked to attend a meeting this morning to resolve the following issue:

Data resides in Oracle.

.NET application pulls relevant data out into an xml file, brings it back to the client which has a sql-server database locally. The data may or may not be updated. If it is, the updates are sent back to Oracle.

Meanwhile there is a complete separate application (not sure what it is implemented in) that needs to be prevented from modifying the data which the .NET application users are currently using. ....the question is how exactly to do this.

....my first impression was to somehow make use of the 'select..for update' and push pl/sql processing but since the data is shipped off via an xml file and the system is already developed, I don't think that's possible. ...the only other option that I can think of (and the one they were already thinking of) is to have a column that indicates whether a rows is locked by some .net user...assuming the data comes from a single table. If the data resides in multiple tables I think that best option is to create a 'data_lock' table that holds the keys from each individual table for the lifetime of the 'transaction'.

Any better/additional ideas?

Not exactly a database centric environment here. :)

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Oct 22 2004 - 07:05:03 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US