[ogsa-dai-users] Extending DQP functionality

[Bruno V. <bru...@gm...>]

Dear community,

A while ago I sent an e-mail suggesting a extension I could make for
OGSA-DAI which is enable write statements (INSERT, UPDATE and DELETE) for
DQP operations. What I want is to provide a more transparent way for the
user to interact with DQP as if these resources were really single tables,
while in fact it is a view composed by several parts of several
tables throughout different databases.

So I thought in enabling write operations (INSERT, UPDATE and DELETE) for
VIEWS (only for those which use DQP resources underneath).

I would like to hear from you how this sounds, how feasible it is and the
overall impact for the community - good and bad ones. Also, if this sounds
too complicated, if there are other solutions to achieve this level of
transparency. And most of all: what would I have to know about the OGSA-DAI
internal components?

Amy once answered a similar question of mine, inquiring supporting INSERT
for DQP, that the following would be needed, and I would like to know if
this answer still proceeds for this "writable views":
"
Then you can write a resource activity for DQP resources which:
 - parses the UPDATE statement and extracts the target table
 - looks up the table location in the DQP data dictionary
 - rewrites the UPDATE statement using the physical table name
 - sends the UPDATE request to the appropriate OGSA-DAI data node
 - handles the results of the request or errors if any
"

Looking forward to suggestions. Have a good day!
-- 
Bruno Velasco