Schema Validators

Schema validators let you export application-facing validation definitions from the same model you use for SQL generation.

What validator export does

DBModeler can generate validator-oriented schemas for multiple libraries, including toolchains such as Zod, Yup, Joi, AJV, TypeBox, ArkType, Typia, and others configured in schemas.json.

This is useful when you want one modeling source for both:

database DDL
application-level validation

Choose a validator target

Open the schema export flow and select the validator library you want.

Each validator has its own rendering rules, setup notes, and type-family mappings, so generated output is library-specific rather than generic.

Choose export scope

Depending on the flow, DBModeler can export:

a full schema set
a single-table schema

This makes it possible to generate a full application layer or only the table you are currently working on.

How field rules are derived

Validator output is based on the modeled field data plus the validator definition file.

That includes:

required versus optional behavior
broad type families
explicit type mappings
check-related narrowing where the validator supports it

Auto-generated database fields are often excluded so the exported validator does not reject values the database creates for you.

Limits to keep in mind

Not every validator supports every DB constraint pattern.
Some libraries require extra setup code outside the exported file.
Complex DB-native behavior may map to broader runtime validation types.

Recommended workflow

finalize the table structure
review SQL output first
export the validator schema
verify any setup notes required by the selected library

Next: Catalog Configuration