i want to know what is "prodataset" and what is the use of it-Urgent

When I answered the post it was in chat.

I think. (I checked PT about 20 mins after I posted and it was in development, and I couldn't see mention of 'moved', so maybe I'm seeing things, in which case sorry subramanian).
 
im still new to this and id also be happy to hear what you guys have to say
on the subject.

i mostly browsed thru the oera whitepapers and docs and still have alot of
catching up to do.


prodatasets are mostly used as a service data object.

with in a distributed architecture the client mostly works detached from the
data source.

the client requests the data from the appserver, makes changes to the data
and passes it back to be saved.

prodatasets lets you move complex data structures back and forth.


the term in-memory database doesn't sit well with me. i prefer complex
data structure.

because the data is mostly joined and although it doesnt have to be,
the data is usually related.

prodatasets also map closely to ado.net, java service-data-object (sdo)
and xml for passing data between diff platforms.


the dataset and temp-tables are whats called the logical view, what the
app works with.

and are attached to a data source, what fills in the data, saves it back
and from where.

this separation from logical view and data source allows to switch (or even
combine) between diff data sources.

without the need to make any changes to the app.


for example, progress database can be switched with an oracle dataserver
or an xml file, not even a database.

another example, is making changes to the underline schema without the
need to make changes to the rest of app.
 
Back
Top