Drive in Motion: Handling Data Object Changes

On my personal blog at dbvt.com I posted on using Drive to handle data object changes in Community Server Development.  The screenshots include adding the field to the SQL utility table, regenerating the Business Object with the new project, the PopulateDataObject() method, and the creation of SQL Command Parameters.  I don't like reposting, so you'll find the original post here.

One addition I wanted to add here on the driveframework.com blog was elaborate on the term "SQL utility table."  The CodeSmith templates in Drive are very SQL Table-centric.  Custom data objects in Community Server or other applications rarely represent a single table, but are more like "strongly typed views."  For Drive users, a standard practice when updating data objects would be to update the SQL table, update the view, then perform a

select * into z_SomeTable from drive_vw_SomeView

thus creating a SQL Utility Table that the Drive CodeSmith templates can use to generate code based on the table's data types. In this instance, the SourceTable of the template would be "z_SomeTable."

Please let me know if you have any questions about creating SQL Utility Tables for Drive or the role of SQL tables in Drive.