SQLPage v0.17.1 documentation

If you are completely new to SQLPage, you should start by reading the get started tutorial, which will guide you through the process of creating your first SQLPage application.

Building an application with SQLPage is quite simple. To create a new web page, just create a new SQL file. For each SELECT statement that you write, the data it returns will be analyzed and rendered to the user. The two most important concepts in SQLPage are components and parameters.

To select a component and set its top-level properties, you write the following SQL statement:

SELECT 'component_name' AS component, 'my value' AS top_level_parameter_1;

Then, you can set its row-level parameters by writing a second SELECT statement:

SELECT my_column_1 AS row_level_parameter_1, my_column_2 AS row_level_parameter_2 FROM my_table;

This page documents all the components provided by default in SQLPage and their parameters. Use this as a reference when building your SQL application. If at any point you need help, you can ask for it on the SQLPage forum.

If you know some HTML, you can also easily create your own components for your application.


A visually distinctive message or notification.
An advanced component that can be used to create pages with password-restricted access. When used, this component has to be at the top of your page, because once the page has begun being sent to the browser, it is too late to restrict access to it. The authentication component checks if the user has sent the correct password, and if not, redirects them to the URL specified in the link parameter. If you don't want to re-check the password on every page (which is an expensive operation), you can check the password only once and store a session token in your database. You can use the cookie component to set the session token cookie in the client browser, and then check whether the token matches what you stored in subsequent pages.
A versatile button component do display one or multiple button links of different styles.
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.
Sets a cookie in the client browser, used for session management and storing user-related information. This component creates a single cookie. Since cookies need to be set before the response body is sent to the client, this component should be placed at the top of the page, before any other components that generate output. After being set, a cookie can be accessed anywhere in your SQL code using the `sqlpage.cookie('cookie_name')` pseudo-function.
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.
Display all the parameters passed to the component. Useful for debugging: just replace the name of the component you want to debug with 'debug'.
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.
For advanced users, allows you to easily build an API over your database. The json component responds to the current HTTP request with a JSON object. This component must appear at the top of your SQL file, before any other data has been sent to the browser.
A vertical list of items. Each item can be clickable and link to another page.
Displays a map with markers on it. Useful in combination with PostgreSQL's PostGIS or SQLite's spatialite.
Redirects the user to another page. This component is useful for implementing redirects after a form submission, or to redirect users to a login page if they are not logged in. Contrary to the http_header component, this component completely stops the execution of the page after it is called, so it is suitable to use to hide sensitive information from users that are not logged in, for example. Since it uses an HTTP header to redirect the user, it is not possible to use this component after the page has started being sent to the browser.
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.
Build a tabbed interface, with each tab being a link to a page. Each tab can be in two states: active or inactive.
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.
A list of events with a vertical line connecting them.

The "shell" component

Personalize the "shell" surrounding your page contents. Used to set properties for the entire page.

Top-level parameters


The URL of a CSS file to load and apply to the page.


A description of the page. It can be displayed by search engines when your page appears in their results.


Name of a font to display the text in. This has to be a valid font name from fonts.google.com.


Font size on the page, in pixels. Set to 18 by default.


Muted text to display in the footer of the page. This can be used to display a link to the terms and conditions of your application, for instance. By default, shows "Built with SQLPage". Supports links with markdown.


Name of an icon (from tabler-icons.io) to display next to the title in the navigation bar.


The URL of an image to display next to the page title.


The URL of a Javascript file to load and execute on the page.


The language of the page. This can be used by search engines and screen readers to determine in which language the page is written.


The target of the link in the top navigation bar.


Adds a menu item in the navigation bar at the top of the page. The menu item will have the specified name, and will link to as .sql file of the same name. A dropdown can be generated by passing a json object with a `title` and `submenu` properties.


Forbids robots to save this page in their database and follow the links on this page. This will prevent this page to appear in Google search results for any query, for instance.


Number of seconds after which the page should refresh. This can be useful to display dynamic content that updates automatically.


When this is set, a search field will appear in the top navigation bar, and load the specified sql file with an URL parameter named "search" when the user searches something.


Set to "dark" to use a dark theme.


The title of your page. Will be shown in a top bar above the page contents. Also usually displayed by web browsers as the name of the web page's tab.

Example 1

This example contains the values used for the shell of the page you are currently viewing.

The menu_item property is used both in its simple string form, to generate a link named "functions" that points to "functions.sql", and in its object form, to generate a dropdown menu named "Community" with links to the blog, the github repository, and the issues page.

The object form can be used directly only on database engines that have a native JSON type. On other engines (such as SQLite), you can use the dynamic component to generate the same result.

    'shell'                   as component,
    'SQLPage documentation'   as title,
    '/'                       as link,
    JSON('{"link":"index.sql","title":"Home"}') as menu_item,
    JSON('{"title":"Community","submenu":[{"link":"blog.sql","title":"Blog"},{"link":"//github.com/lovasoa/sqlpage/issues","title":"Issues"},{"link":"//github.com/lovasoa/sqlpage/discussions","title":"Discussions"},{"link":"//github.com/lovasoa/sqlpage","title":"Github"}]}') as menu_item,
    'functions'               as menu_item,
    'components'              as menu_item,
    'en-US'                   as language,
    'Documentation for the SQLPage low-code web application framework.' as description,
    'Poppins'                 as font,
    'book'                    as icon,
    'https://cdn.jsdelivr.net/npm/prismjs@1/components/prism-core.min.js' as javascript,
    'https://cdn.jsdelivr.net/npm/prismjs@1/plugins/autoloader/prism-autoloader.min.js' as javascript,
    '/prism-tabler-theme.css' as css,
    'Official [SQLPage](https://sql.ophir.dev) documentation' as footer;

Official SQLPage documentation