The two most important concepts in SQLPage are components and parameters. This page documents all the components that you can use in SQLPage and their parameters. Use this as a reference when building your SQL application.
A visually distinctive message or notification.
A grid where each element is a small card that displays a piece of data.
A component that plots data. Line, area, bar, and pie charts are all supported. Each item in the component is a data point in the graph.
A button that lets the user download data as a CSV file. Each column from the items in the component will map to a column in the resulting CSV.
Display small pieces of information in a clear and readable way. Each item has a name and is associated with a value.
A special component that can be used to render other components, the number and properties of which are not known in advance.
A series of input fields that can be filled in by the user. The form contents can be posted and handled by another sql file in your site. The value entered by the user in a field named x will be accessible to the target SQL page as a variable named $x. For instance, you can create a SQL page named "create_user.sql" that would contain "INSERT INTO users(name) VALUES($name)" and a form with its action property set to "create_user.sql" that would contain a field named "name"."
Display a large title and description for your page, with an optional large illustrative image. Useful in your home page, for instance.
An advanced component that can be used to create redirections, set a custom caching policy to your pages, or set any HTTP header. If you are a beginner, you probably don't need this component. When used, this component has to be the first component in the page, because once the page is sent to the browser, it is too late to change the headers. Any valid HTTP header can be used as a top-level parameter for this component. HTTP headers are additional pieces of information sent with responses to web requests that provide instructions or metadata about the data being sent — for example, setting cache control directives to control caching behavior or specifying the content type of a response.
A vertical list of items. Each item can be clickable and link to another page.
Personalize the "shell" surrounding your page contents. Used to set properties for the entire page.
Guide users through multi-stage processes, displaying a clear list of previous and future steps.
A table with optional filtering and sorting. Unlike most others, this component does not have a fixed set of item properties, any property that is used will be rendered directly as a column in the table.
A paragraph of text. The entire component will render as a single paragraph, with each item being rendered as a span of text inside it, the styling of which can be customized using parameters.