Well-normalized database structures work best since Iron Speed Designer creates a suite of pages for each database table and view you select. Well-normalized databases have explicitly defined tables to express most concepts, making it easy for Iron Speed Designer to create a more comprehensive application.
Iron Speed Designer creates master-detail (parent-child) pages based on the one-to-many relationships in your database. For example, one order may have multiple line items. Accordingly, a well-structured database would have both an Orders table (master) and an OrderDetails table (detail). A foreign key field in the OrderDetails table identifies the parent record in the Orders table.
When Iron Speed Designer creates web pages for the Orders table, it will automatically join the OrderDetails table and include it as a separate panel on the page, creating a master-detail page.
Examples:
|
Master / parent / one |
Detail / child / many |
|
|
Customers.CustomerID |
Orders.CustomerID |
one customer may have many orders |
|
Orders.OrderID |
OrderDetails.OrderID |
one order may have many line items |
Step 1a: Create child tables for one-to-many relationships
Step 1b: Create separate lookup tables
Step 1c: Create database views to express multi-table joins and complex queries
Step 1d: Explicitly declare primary keys in your database
Step 1e: Explicitly declare foreign keys in your database
Step 1f: Declare virtual primary keys in Iron Speed Designer
Step 1g: Declare virtual foreign keys in Iron Speed Designer