DBI Warehouse Shipments Scheduling
Framework -
Databinding
Three methods of Databinding
The dbiWSF ships with
two types of databases, MSSQL and MSAccess
(as detached databases). There are clean tables and test tables that include sample test data. In addition to the databases a Database Structure
a PDF file is also included so the default tables can be recreated in another ADO.Net compliant database.
Rapid Application Development
The databinding layer is a key factor of the Warehouse Shipments Framework
providing a flexible data model that would accommodate Rapid Application Development without
many of the drawbacks found in default databinding models available in .NET.
The framework incorporates a mechanism to tie the object layer to the databinding layer using reflection. This is pre-coded for SQL or OLE ADO adapters,
using the default table structure or the built in Column Mapping feature (CMAP)
developers can essentially configure the data simply by
setting the connection string to point at the database.
As the source for this is included you can marshal your own datatypes easily or go with the built-in generic types. Every effort has been made to keep the types as generic as possible to avoid the necessity of changing the mapping or corrupting the reflection.
The framework includes three methods of databinding available for each type of database:
-
Standard
-
InMemory
-
Custom.
These methods relate to the style of
loading data. The Standard type uses very sequential select statements. These commands load the data in the same structure as the objects themselves, which is not optimized in any way. This is slower but much easier to read.
The InMemory method loads all of the data for
a specified period then uses LINQ to parse that data into the specified objects. This is very
fast as the only load on the database engine is to select by
date range with a couple of inner joins. InMemory is the default databinding method for its combination of performance and readability.
Finally the Customized databinding option is designed for database administrators or for those that have large datasets to setup and persist the data through optimized queries, indexing or even for XML datasets. This option
provides more control over the database speed and use the integrated databinding options available.
Single User and Multi-User
Environments
While the dbiWSF is coded for single user solutions, consideration
has been provided for multi-user environments. As such the Try-Catch statements for the databinding have been setup with concurrency catches. These catches allow the developer to code concurrency issues in a manner specific to their implementation.
For more detailed information on Databinding please see the source code for full documentation, the source code for the sample application that ships with the product, or use the project template to start using the functionality
right out of the box.
|