DDL to code

Generate Repository, Application, and Api code from a DDL file.

Upload a validated text file, set the namespace prefix, and download the generated code package. The generator keeps audit rules, DTO output, validators, and reports aligned.

.txt upload only audit-aware output zip download
Generator

Generate code package

Use at least 2 characters. Only English letters and dots are allowed.
This field can be left empty. You can also enter multiple prefixes separated by commas; the matching prefix is removed before the table name is converted to an entity name.
No file selected
Only .txt files are accepted, and the uploaded content is validated for DDL syntax and structural correctness before generation starts.
Download demo DDL
Overview

Generation notes

  1. Standard business tables generate Repository, Application, and Api code. Relation tables such as *_relation still generate entity classes, entity configs, and entity-to-table mappings, but they do not generate CRUD services or controllers.
  2. Every table must define id bigint. Audit inheritance only supports these exact combinations: id, id + createby + createtime, or id + createby + createtime + modifyby + modifytime.
  3. Entity names are derived from table names after optional prefix stripping. Table names treat ., -, and _ as word separators, while schema-qualified names are preserved for ToTable(...) mappings.
  4. Generated DTOs exclude inherited audit fields, IsDeleted, and RowVersion. Output DTOs inherit OutputDto, OutputBaseAuditDto, or OutputFullAuditInfoDto based on the detected audit pattern.
  5. String column lengths are reused in entity configs, validation rules, and optional EntityConsts. Unique constraints become duplicate checks only when every constrained column is included in DTO generation.
  6. The downloaded zip includes layered source output under src plus a generation-report.txt file that records generated tables and relation tables without CRUD output.
Workflow

Recommended steps

01
Download the demo file

Use the sample DDL to verify naming, audit inference, and relation table behavior before uploading your own schema.

02
Set namespace and prefixes

Keep the namespace clean and strip any shared table prefixes so generated entities read naturally.

03
Generate and integrate

Review the zip package, then copy the generated layers and the report into your target solution.