1.3.1
Released on Mar 15, 2024
Bug fixes:
Add JWT ID claim to tokens issued by SurrealDB.
Consistently enforce session expiration.
Upgrade or install
Get SurrealDB v1.3.1
Pick how you want to install or upgrade. Surrealist can update connected instances in place, or choose a platform below to copy a CLI command for v1.3.1.
You can upgrade your SurrealDB Cloud instance to v1.3.1 effortlessly through the Surrealist app.
- Open the Surrealist app
- Select your organisation and instance
- On the dashboard, click on the "Upgrade" button
- Your instance will be updated and restarted automatically
1.3.0
Released on Mar 12, 2024
Features:
Introduced
IF NOT EXISTSclause onDEFINEstatements.Implemented
IF EXISTSfor additionalREMOVEstatements.Changed the KNN operator from
<2>to<|2|>in the new parser and added support in the old parser for the new syntax.Implemented WebSocket session expiration.
Added support for tables and geometries in CBOR.
Added support for parsing decimal numbers with scientific notation.
Added support for printing a warning in the CLI when using an outdated version of SurrealDB.
Added
Surreal::wait_forto make it possible for the client to wait for certain events.Added SurrealKV as an unstable feature.
Added more error message improvements for the new parser.
Bug fixes:
More consistent handling of negative numbers in record IDs.
Removed the unimplemented
backupcommand from the CLI.Fixed document not being available to delete permissions clause.
Ensured objects properties are recognised by the query planner.
Implemented the union strategy on unique indexes.
Performance improvements:
Added compile-time feature for flamegraph and pprof profiling.
IF NOT EXISTS clause on DEFINE statements
DEFINE statements now allow you to include an IF NOT EXISTS clause which ensures that the define statement is only run if the resource doesn't already exist. If it exists, you will get an error. Learn more about this in the documentation.
New KNN syntax
The KNN operator now supports a new syntax using <| and |> instead of < and >. Learn more about this in the documentation
Waiting for client events
It's now possible to initialise the connection and run setup actions like authentication and selecting the database concurrently with other queries by making it possible to wait for the SDK to connect or select the database to use before allowing other queries to execute.
Something like this would be susceptible to a race condition before:
Now it's possible to make the client wait for either the connection to be established
or the database to be selected.
Newer patch available
Upgrade to 1.3.1
You are viewing the 1.3.0 changelog. A newer patch in this release line is available - we recommend running 1.3.1 for the latest fixes and improvements.
Our newsletter
Get tutorials, AI agent recipes, webinars, and early product updates in your inbox every two weeks