v0.15.0

• New functions: sqlpage.path(), sqlpage.variables()
  • sqlpage.variables() makes it easier to process forms with a variable number of fields (for instance, when the form fields themselves are generated based on data from the database). See the online shop orders example.
• bug fixes
  • Most notably, a serious bug was fixed where variables and function evaluation results were truncated in Microsoft SQL Server.
  • fixed some missing sql support:
    • FILTER clauses in window functions
    • MySQL-specific REGEXP syntax
• improved documentation
• new align_right attribute in the table component

v0.15.0-beta.0

First beta-release for v0.15

v0.14.0

button component and time series plots

• Better support for time series in the chart component. You can now use the time top-attribute to display a time series chart
  with smart x-axis labels.
• 
• New component: button. This allows you to create rows of buttons that allow navigation between pages.
  • 
• Better error messages for Microsoft SQL Server. SQLPage now displays the line number of the error, which is especially useful for debugging long migration scripts.
• Many improvements in the official website and the documentation.
  • Most notably, the documentation now has syntax highlighting on code blocks (using prism with a custom theme made for tabler). This also illustrates the usage of external javascript and css libraries in SQLPage. See the shell component documentation.
  • Better display of example queries in the documentation, with smart indentation that makes it easier to read.
• Clarify some ambiguous error messages:
  • make it clearer whether the error comes from SQLPage or from the database
  • specific tokenization errors are now displayed as such

v0.13.0

v0.13.0: beautiful timelines and scatter plots

• New timeline component to display a timeline of events.
• Add support for scatter and bubble plots in the chart component. See the chart documentation.
• further improve debuggability with more precise error messages. In particular, it used to be hard to debug errors in long migration scripts, because the line number and position was not displayed. This is now fixed.
• Better logs on 404 errors. SQLPage used to log a message without the path of the file that was not found. This made it hard to debug 404 errors. This is now fixed.
• Add a new top_image attribute to the card component to display an image at the top of the card. This makes it possible to create beautiful image galleries with SQLPage.
• Updated dependencies, for bug fixes and performance improvements.
• New icons (see https://tabler-icons.io/changelog)
• When NULL is passed as an icon name, display no icon instead of raising an error.
• Official docker image folder structure changed. The docker image now expects
  • the SQLPage website (.sql files) to be in /var/www/, and
  • the SQLPage configuration folder to be in /etc/sqlpage/
  • the configuration file should be in /etc/sqlpage/sqlpage.json
  • the database file should be in /etc/sqlpage/sqlpage.db
  • custom templates should be in /etc/sqlpage/templates/
  • This configuration change concerns only the docker image. If you are using the sqlpage binary directly, nothing changes.

Full Changelog: v0.12.0...v0.13.0

v0.12.0

SQLPage Release Notes - Version 0.12.0 🚀

SQLPage is a small web server that renders your SQL queries as beautiful interactive websites. This releases brings exciting features that should make development even easier, faster, and more secure. Let's dive into the exciting innovations of version 0.12.0:

🧮 Variable Support

SQLPage now empowers you with the ability to set and reuse variables between SQL statements. This dynamic feature allows you to craft more complex SQL queries and reuse query results across multiple places in your code. Here's a sneak peek:

-- Set a variable 
SET person = (SELECT username FROM users WHERE id = $id); 
-- Use it in a query 
SELECT 'text' AS component, 'Hello ' || $person AS contents;

🚀 Execute Server-Side Commands with sqlpage.exec

Introducing sqlpage.exec—a powerful function that lets you execute commands on the server. This opens up a world of possibilities, from making external API calls to sending emails and running custom code on the server. Be creative, but remember that with great power comes great responsibility !

SELECT 'card' AS component;
SELECT 
    value->>'name' AS title, 
    value->>'email' AS description 
FROM json_each(sqlpage.exec('curl', 'https://jsonplaceholder.typicode.com/users'));

🛡️ Security

For your security, the sqlpage.exec function is disabled by default. To enable it, simply set the allow_exec configuration parameter to true in the configuration. Please use caution, as enabling this function grants significant server access to anyone who can write SQL queries on your website.

🍔 Menu Items Made Easy

Configuring multiple menu items has never been simpler. Now, syntax like

SELECT 'shell' AS component, '["page 1", "page 2"]' AS menu_item

works as expected. See

• the shell component documentation
• the small SQL game example
• and join the discussion here.

🛠️ Database Connection Setup: on_connect.sql

Create the sqlpage/on_connect.sql file to run a SQL script on each database connection before it's used. This versatile feature enables you to customize your database connection with settings like PRAGMA in SQLite, custom variables in PostgreSQL, and more. Explore the endless possibilities!

🚧 Improved Error Handling

Experience more precise and informative error messages with SQLPage. When an error occurs, you'll now receive detailed error positions within the SQL statement. Say goodbye to vague error messages and welcome efficient debugging.

📟 ARM: Hello, Raspberry Pi and Mac M1 Users!

SQLPage now distributes Docker images for ARM architecture, expanding your possibilities for deployment. Whether you're using a Raspberry Pi or a Mac M1, SQLPage is ready to power your projects!

🔒 Enhanced Security by Default

To enhance security, SQLPage now creates the default SQLite database file in the "sqlpage" config directory, making it inaccessible from the web by default. For those who prefer the previous behavior, simply set the database_url configuration parameter to sqlite://sqlpage.db in your configuration.

📜 Empty List Customization

Tailor your list components with precision using the new empty_title, empty_description, and empty_link top-level attributes in the list component. Now you have full control over the text displayed when your list is empty.

🔒 Asynchronous Password Hashing for Enhanced Performance and Security

Say goodbye to request processing bottlenecks! SQLPage used to block a request processing thread while hashing passwords, potentially leaving your site vulnerable to denial of service attacks. Not anymore! SQLPage now launches password hashing operations on a separate thread pool, allowing your application to handle other requests while efficiently hashing passwords.

🔗 URL Parameter Encoding

Introducing sqlpage.url_encode! This function simplifies URL parameter encoding, making it a breeze to create dynamic URLs in your web application.

SELECT 'card' AS component; SELECT 'More...' AS title, 'advanced_search.sql?query=' || sqlpage.url_encode($query)

Upgrade

Upgrade to SQLPage 0.12.0 and elevate your web development game to new heights. We're committed to providing you with the tools and features you need for a seamless, efficient, and secure coding experience.

Get Started with SQLPage | GitHub Repository

Unleash your creativity, streamline your development, and craft extraordinary SQL-driven web applications with SQLPage 0.12.0. Happy coding! 💻🚀

v0.12.0-beta4

Better error messages

v0.12.0-beta3

new feature: sqlpage/on_connect.sql to run sql statements at the begi…

v0.12.0-beta2

Beta 2, fixes bugs with non-string variables and

introduces sqlpage.exec

v0.12.0-beta

v0.12 Beta release

• variables . SQLPage now support setting and reusing variables between statements. This allows you to write more complex SQL queries, and to reuse the result of a query in multiple places.

  -- Set a variable
  SET person = 'Alice';
  -- Use it in a query
  SELECT 'text' AS component, 'Hello ' || $person AS contents;

v0.11.1

⚠️ Security update

Fixes a potential exposure of database credentials if they are in the configuration file (not in an environment variable), and the web_root is the current working directory (the default). See #89

Full Changelog: v0.11.0...v0.11.1