FcDesigner v3.6 Adds SQL Export, Letting Visual Forms Become Database Tables Directly
Teams running low-code form workflows in Vue now have a direct path from visual form design to database schema, which removes a manual translation step that usually introduces drift between the form and its backing table. The diff capability makes the generated SQL reviewable against prior state instead of blindly destructive.
FcDesigner v3.6 ships a new SQL generation panel in its preview dialog. The panel produces CREATE TABLE statements from the current form and compares them with historical table structures, outputting change statements for added/removed tables and fields, modified fields, and renames. A required flag on a field is the only condition that triggers NOT NULL in the generated SQL, and the designer exposes getSQL and getSQLDiff methods for use from business code.
The release also upgrades tooltip editing to accept raw HTML, with a read-only input and a popup editor when line breaks are present, requiring formCreate 3.3.6+ or 2.7.32+. New button group components land for Element Plus and Ant Design Vue, letting a set of buttons share size and type configuration while each button's text stays individually editable, and Element Plus adds text-button styling with background color options. The preview dialog's four panels (form, components, HTML, SQL) can each be toggled on or off, and table form column headers now follow the designer's multi-language setup.
UI polish includes descriptive text in validation rule dropdowns and placeholder examples in the event/custom-validation editors. Component-level additions cover Ant Design Vue select search with label-or-value matching, Element Plus tree disable configuration, and a Vant select clear icon.
Generating SQL directly from a visual form makes the schema a byproduct of the UI, which can speed up prototyping but risks baking form-level assumptions into the database layer without a human review step.
The diff-based SQL output positions the tool for iterating on existing forms, since teams can see the exact migration statements rather than regenerating tables from scratch.
Supporting HTML in tooltips is a power feature, but it asks teams to trust the renderer with raw markup, which may create a sanitization obligation depending on where the content originates.