Originally created by: jamieogl...@gmail.com
Originally owned by: jamieogl...@gmail.com
The definition will contain a database header naming the database. This is expected to match the complete database definition.
For each stored procedure defined, we have a header containing a local name, the schema and procedure name, and a list of tables returned in sequence, and a list of parameter values. The local name allows for scenarios where different results are returned for different sets of parameters. It is also anticipated that the local name will be used to name the strongly typed dataset class generated from this definition.
The parameters will be used for testing purposes, and potentially for interactively defining the generator data.
For each table, we nave the table name and optionally a database schema and table name.
We have a list of primary key columns, each entry being a column name.
We have a list of foreign references.
Each reference will have the name of the table referred to, and an indicator if the reference can be enforced immediately (the default) or after the data has been loaded. Also indicators if key changes are to be cascaded, and if header record deletions can be cascaded.
It will also have a list of key column matches.
Apart from key columns, no columns will be named.
The parameters will be name and value pairs.