Kevin,

Good start.

Some of these seem more like internals -- though it's worthwhile to
document them I wonder if they fit in a user's guide. Change history
processing is a good example. Is there anything the user needs to know
about this other than the fact that the DAS manages everything?
Partial update is along the same lines - it isn't something a user
needs to know about to write an application.

It might be nice to organize things in terms of "How to" sections..
eg, "How to use static SDO Types" or "How to map database table and
column names to SDO types and properties".

I would extend converters to cover general data type issues,
especially with respect to conversion from the database to SDO types.

I'm not sure the ordering is much of an issue. It seems that beyond
the basic read/write scenario most subjects deal with how to enable a
more specific scenario. The exception would be the convention section
which is pretty broad.

Brent

On 9/28/06, Kevin Williams <[EMAIL PROTECTED]> wrote:
Here is the initial list of capabilities I would like to document from a
users perspective.  I am not sure if this is the best ordering since I
want it to be in order of relevance and also in the order that a new
user might need to make use of the DAS.  Any suggestions?


Capabilities

   * Reading and writing to the database - Basic CRUD
     
<http://wiki.apache.org/ws/Tuscany/TuscanyJava/DAS_Java_Overview/RDBDAS_Java_User_Guide/Basic_CRUD>

   * Change History Processing
   * Optimistic Concurrency Control
   * Generated Database Keys
   * Stored Procedures
   * Write Operation Ordering
   * Column Converters
   * Paging
   * Working with static DataObjects
   * Working with compound keys
   * Object Relationships
   * Name Mapping (aliasing)
   * Convention over configuration
   * Logging
   * Partial Update
   * Explicit CREATE/UPDATE/DELETE
   * Working with transactions
   * Explicit ResultSet shape definition

Thanks,

--Kevin


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to