XSLT for transforming an XML doc into DDl statements for schema population

100%

XSLT for transforming an XML doc into DDl statements for schema population

✓ Published0🌍 Public

Last edited May 18, 2021

Created on May 18, 2021

This example demonstrates an XSLT 1.0 stylesheet that transforms an XML DataSet schema into SQL DDL statements for creating database tables. It shows how to generate `CREATE TABLE` commands with identity columns, foreign key constraints, and primary key handling from XSD-defined complex types. The transformation uses XSLT templates, variables, and the `document()` function to process included schemas, while the `xsl:output method="text"` produces plain SQL text. The stylesheet maps XML schema types to SQL data types via a custom `Types` template, iterating over field elements and attributes to build column definitions.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 8ddacfa41ce888f458863185ecfc400f

This example demonstrates a stored procedure that converts XML data into relational rows for insertion into a database table. The code defines `usp_InsertDemoXML`, which accepts a `varbinary(max)` parameter, casts it to XML, and then uses XQuery’s `nodes()` and `value()` methods to extract `key` and `value` pairs from each `<row>` element. It shows a data-ingestion pattern for parsing structured XML payloads into a normalized key-value table structure. The procedure relies on T-SQL’s built-in XML support rather than external visualization libraries, focusing on server-side data transformation.

HHugoberry

61% match

Loading thumbnail…

Dummy table serialized as XML binary

This example shows a Power Query routine that serializes a two-column table into a single binary XML document. The code transforms each row into a `<row>` element containing `<key>` and `<value>` tags, then wraps all rows in a root `<table>` element. It relies on the `Table.TransformRows` function to iterate over the input table, while `Binary.Combine` and `Text.ToBinary` concatenate the textual XML fragments into a single binary output. The data source is an in-memory table named `dummy`, and the result is a well-formed XML representation of that table.

HHugoberry

59% match

Loading thumbnail…

Searializing a table into and XML string in Power Query

This example demonstrates how to flatten a tabular dataset into a single XML string using Power Query’s M language. It shows the transformation of a table’s records into nested `<row>` elements wrapped in a top-level `<table>` tag. The code relies on `Table.ToRecords`, `List.Accumulate`, and `Record.FieldNames` to iterate over rows and columns, dynamically generating tags with `Text.Format`. Field names and values are inserted into `<#0>` and `</#0>` placeholders, producing a structured XML output. The approach is purely functional, avoiding loops, and directly serializes the table’s content into a text-based hierarchical format.

HHugoberry

56% match

Loading thumbnail…

Schematron example

This example demonstrates how Schematron rules enforce document constraints, reporting human-readable diagnostics for missing or invalid data. It shows two validation patterns: one requiring an `authorized` attribute on `author` elements, and another ensuring `date` elements contain valid `xs:gYear` values. The schema uses Schematron’s `rule`, `assert`, and `diagnostics` elements, with XPath expressions like `text() castable as xs:gYear` and `../title/text()` to locate context and produce tailored error messages. The source is an XML file defining validation logic, not a graphical visualization, so no rendering libraries or canvas APIs are used.

CCliffordAnderson

56% match

Loading thumbnail…

<title>Testing XPath

This example demonstrates how XPath and the XQuery `typeswitch` expression can be used to selectively process different node types in an XML document. It shows a TEI-encoded text where comments, text nodes, and `<p>` elements are handled distinctly, with element attributes joined into a space-separated string. The code relies on the XQuery 3.0 standard library functions `fn:string` and `fn:string-join`, operating on the TEI namespace declared in the document. The visualization is static, with no graphical rendering; instead, it highlights the programmatic traversal and conditional branching over the XML tree structure.

CCliffordAnderson

55% match

Loading thumbnail…

Gist be32a2ac117700d3dbde6b0824367ba5

This example demonstrates how to create a simple database table visualization from a SQL schema definition. The code defines a `Demo` table with three columns—`ID`, `Key`, and `Value`—and shows how to map those column types and constraints into a visual entity-relationship style diagram. Using the provided `CREATE TABLE` statement as the data source, the visualization renders each column as a node, with the primary key and nullable attributes indicated through distinct visual encodings. The implementation leverages `d3.forceSimulation` for the node layout and `d3.geoPath` for any geometric rendering, while relying on standard DOM elements for interactivity. No additional behavior beyond the table’s structural representation is implied.

HHugoberry

55% match

Loading thumbnail…

XMLA script to surface all DAX function definitions for SSAS

This example shows how to surface all DAX function definitions for SQL Server Analysis Services by issuing an XMLA Execute command. The code queries the `$SYSTEM.MDSCHEMA_FUNCTIONS` schema rowset, filtering for rows where `Origin` is 3 or 4, which correspond to DAX functions. It retrieves fields such as function name, parameter info, description, interface name, and library name. The request targets a specific catalog ID and uses the standard XMLA namespace. This is a direct data-extraction approach, not a visualization library, but it produces the raw metadata needed to build any downstream chart or graph of DAX functions.

HHugoberry

55% match

Loading thumbnail…

<title>Testing XPath

This example demonstrates how an XML TEI document’s structure can be queried using XPath and represented as an interactive node-link diagram. It displays the document’s hierarchical elements—such as `teiHeader`, `text`, `body`, and `p`—as circles connected by links, with text content visible alongside node labels. The visualization uses D3.js’s `d3.hierarchy` and `d3.tree` layout to calculate positions, while `d3.zoom` enables panning and zooming. The code loads the XML via a local file and parses it with `DOMParser`, then applies XPath expressions via `document.evaluate` to extract elements and text for rendering.

CCliffordAnderson

54% match