Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.
The following page has been changed by KevinWilliams: http://wiki.apache.org/ws/Tuscany/TuscanyJava/DAS_Java_Overview/RDBDAS_Java_User_Guide/Convention_over_configuration ------------------------------------------------------------------------------ = Convention over configuration = - This concept reflects the notion that configuration (defining a bunch of stuff in a side file) can be avoided by following convetion (adhering to prescribed patterns) and that this is generally a good thing. The RDB DAS has several reasonable conventions in place and using these can significantly reduce a developers work-load. + This concept reflects the notion that configuration (defining a bunch of stuff in a side file) can be avoided by following convention (adhering to prescribed patterns) and that this is generally a good thing. The RDB DAS has several reasonable conventions in place and using these can significantly reduce a developer's work-load. + + As an example, the RDB DAS provides a straight-forward, one-to-one mapping of database tables to !DataObject Types and from table columns to !DataObject properties. If a user provides no mapping information to the contrary, when a an application reads a graph of !DataObjects the Types/Properties returned in the graph will directly reflect the Tables/Columns queried. + + For example, consider a database with the following table: + {{{ + TABLE CUSTOMER + ID INTEGER + LASTNAME VARCHAR(20) + ADDRESS VARCHAR(30) + }}} + + As an example, the RDB DAS must know how a !DataObject's properties map to a database table key in order to generate the INSERT/UPDATE and DELETE statements necessary to flush a data graph's changes to a database. In typical Object/Relational mappings frameworks, this information is provided in a config file with something like this: --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
