include-sql is a macro for using SQL in Rust.
include-sql was inspired by Yesql. It allows the programmer to write SQL queries in SQL, keep them separate from the Rust code, and easily embed them into Rust programs via the proc-macro that this library provides.
All by itself include-sql actually does very little - it reads and parses SQL file and transforms it into a call to the impl_sql
macro. It is expected that impl_sql
is provided either by the project that uses include-sql or by an external library. For example, there are several include-sql companion crates, like include-postgres-sql, include-sqlite-sql, and include-oracle-sql, that implement impl_sql
. They can simply be used directly if their approaches to embedding SQL are deemed appropriate and convenient. Alternatively, they can be used as a starting point when implementing your own impl_sql
.
Example
As include-sql is not intended to be used directly, to illustrate the workflow we'll use include-sqlite-sql.
Add include-sqlite-sql
as a dependency:
[]
= "0.2"
Write your SQL and save it in a file. For example, let's say the following is saved as library.sql
in the project's sql
folder:
-- name: get_loaned_books?
-- Returns the list of books loaned to a patron
-- # Parameters
-- param: user_id: &str - user ID
SELECT book_title
FROM library
WHERE loaned_to = :user_id
ORDER BY 1
/
-- name: loan_books!
-- Updates the book record to reflect loan to a patron
-- # Parameters
-- param: book_titles: &str - book titles
-- param: user_id: &str - user ID
UPDATE library
SET loaned_to = :user_id
, loaned_on = current_timestamp
WHERE book_title IN (:book_titles)
/
Note that the parameter order is defined by the
param
declarations.
And then use it in Rust as:
use ;
use ;
include_sql!;
ℹ️ Note that the path to the SQL file can be specified either relative to the project root, i.e. relative to the
CARGO_MANIFEST_DIR
, or relative to the rust module that includes it.
- To specify the path to the included SQL file relative to the project root start the path with the
/
character.- To specify the path to the included SQL file relative to the rust module that included it start the path with the
./
characters.- ⚠️ For compatibility with the legacy code the path to the SQL file can also be specified without
/
or./
prefix. In this case the path to it will be considered to be relative to the project root (as if it was specified with the leading/
).
Under the Hood
After parsing and validating the content of the SQL file include-sql
generates the following call:
impl_sql!
Which include_sqlite_sql::impl_sql
transforms into the following implementation:
And, of course, it also implements the trait:
Documentation
The included documentation describes the supported SQL file format and provides instructions on writing your own impl_sql
macro.
Minimum Supported Rust Version
Since include-sql
0.4 the minimum supported rust version is 1.88 where Span::file() was stabilized.
⚠️ Note that Span::file() when it is called by rust-analyzer, at the time of this writing (version 0.4.2535), returns empty string. This prevents
include-sql
determining the module that called it. While paths relative to the calling module work just fine when projects are compiled by cargo, until Span::file() is fully functional within rust-analyzer, it is advisable to specify included SQL file paths relative to the project root.