The previous post, The Purpose and Classification of Definition Files , laid the definition files out one by one, and FormSchema is the hub among them. Today, a concrete question: when a form queries and when it saves, where do those SQL statements come from?

This post covers:

The six places a new form touches, with zero lines of code

Querying: the join list and paging, both decided on every request

Saving: how a set of fields becomes INSERT, UPDATE and DELETE

Why this is not an ORM, and why the missing pieces are not omissions

The difference between a thousand definitions and a thousand classes

1. One more form, six places to touch

The first post, Why ERP Needs a Definition-Driven Framework , counted adding one field to an existing form.…