Shape Your Schema With Precision

• Intuitive JSON Table Editing: Modify table structures using a familiar treeview interface.
• SQL Syntax Highlighting: Enhances readability for column defaults, expressions, and SQL fragments. Also, available when previewing scripts with the Script Tokens expanded.
• Product and Template Definition Assistance: Simplifies creation and management of reusable schema components.
• Script Token Editing: Customize and manage script tokens efficiently.
• Configurable Script Folders: Organize your scripts according to project structure.
• Advanced Search Capabilities: Quickly locate and navigate to schema elements via name or content search.
• Custom Table Properties supported directly in the UI: See and update your custom table properties in the same editors as the standard properties.
• Live Object Application: Apply changes to objects in real-time during editing.
• Configurable Menu System: Integrate preferred source control tools, alternative editors, and more.
• Configurable integration to source control: Set up the branch file at the Product level, and we'll use it to display your branch name in the status bar. We default to git, but you can configure yours if you use something else.

You can project your own metadata on top of the standard table definition by adding custom properties and types to the table schema. This allows you to do things like add your own documentation property to each table. When you view a table in SchemaHammer you would see this documentation property like it just another property of the table. Upon quenching the table, that property will become available as a TableSchema script token for you to handle in a custom manner at runtime (ie, you could add this documentation as an extended property to the table in question).

In the root of your product, if there is a folder named .json-schemas with a file in it named tables.schema it will be loaded and validated against. SchemaHammer uses this file to drive SchemaHammer editor behavior for custom properties. It can also be useful for setting up a github action to validate your schemas on check-in.