Skip to content

Releases: clockworklabs/SpacetimeDB

Release v2.0.4

11 Mar 18:28
@jdetter jdetter
v2.0.4
8b63d63

Choose a tag to compare

View all tags
Release v2.0.4 Latest
Latest

Hello everyone! This week's release is a small bug-fix patch with a few UX improvements 🎉

New Features

  • The spacetime CLI now checks daily for updates. When an update is available a notice is posted telling the user to upgrade.
  • The spacetime dev project initialization logic now includes a fuzzy search which makes it much easier to find and select a template.

Bug Fixes

  • Fix spacetime login --token falling through to web login
  • Several correctness fixes which could prevent a database from loading

What's Changed

New Contributors

Full Changelog: v2.0.3...v2.0.4

Contributors

kim, bfops, and 10 other contributors
Assets 12
Loading

Release v2.0.3

04 Mar 20:52
@bfops bfops
v2.0.3
5836c26
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Release v2.0.3

SpacetimeDB v2.0.3

We've been getting amazing feedback on our 2.0 release. Today we have a release of small bugfixes and QoL improvements in the CLI and SDK based on some of what we've been hearing. More to come soon!

New features

  • spacetime logs --level filtering. Filter logs by severity with --level warn (that level and above) or --level info --level-exact (exact match only). Works with both text and JSON output. (#4362)

Bug fixes

  • We have improved the latency for making commits durably persisted
  • React: fix useTable isReady stuck on false.
  • TanStack Start: fix useSpacetimeDBQuery returning untyped rows.
  • TypeScript: fix toCamelCase conversion.
  • Fix index truncate edge cases.
  • CLI: preserve leading .. in --out-dir paths.
  • CLI: fix publishing in directories with spaces.
  • CLI: skip upgrade prompt when -y is passed.

C# SDK

  • Improve error messages for Views. Better diagnostics when view queries fail in the C# SDK. (#4435)

What's Changed

New Contributors

Full Changelog: v2.0.2...v2.0.3

Contributors

drogus, bfops, and 11 other contributors
Loading

Release v2.0.2

26 Feb 19:54
@bfops bfops
v2.0.2
bc4fcec
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Release v2.0.2

SpacetimeDB v2.0.2

A bug fix and quality-of-life release following the 2.0 launch. This release focuses on CLI improvements, durability tuning, and documentation fixes.

Bug fixes

  • TypeScript: fix table schema wire name lookup crash. The TypeScript SDK was using PascalCase accessor names for wire protocol lookups, causing crashes when case conversion was enabled. (#4449)
  • spacetime dev: fix file watcher ignoring --module-path. When --module-path was set via CLI flag or spacetime.json, the file watcher still watched the default directory instead. (#4464)
  • spacetime dev: better error when module directory does not exist. Previously showed a confusing "could not detect language" error. Now shows the actual missing path. (#4467)
  • Fix "Press any key to exit" in templates. The prompt said "any key" but actually required Enter. Updated text and logic to match. (#4468)
  • Don't save source_config to spacetime.json. Internal build configuration was being persisted to the user-facing config file. (#4422, #4423)

Performance

  • Reduce local durability fsync interval to 10ms (down from misconfigured 500ms default), improving confirmed reads latency for local (non-replicated) databases. (#4466, #4420)
  • C# SDK: ArrayPool for row iteration buffers. RawTableIterBase.Enumerator now rents from ArrayPool<byte>.Shared instead of allocating a fresh byte[] per step, significantly reducing GC pressure. (#4385)

Documentation

  • Correct unique indexes in cheat sheet to use filter, not find. (#4452)
  • Correct "table" to "view" in Zen of SpacetimeDB. (#4434)
  • Update C# docs with List<T> returns and IEnumerable<T> examples. (#4392)
  • Fix AI assistant rules links in llms.txt. (#4430)
  • Add ARM M-series CPU note in benchmark readme. (#4426)
  • Add schedule name correction for LLM rules. (#4370)
  • Fix Spacerace button and rename nav item to Referrals. (#4458, #4477)

What's Changed

Full Changelog: v2.0.1...v2.0.2

Contributors

drogus, kim, and 13 other contributors
Loading

SpacetimeDB 2.0

20 Feb 22:03
@jdetter jdetter
v2.0.1
a4d29da
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
SpacetimeDB 2.0

SpacetimeDB 2.0 is finally here! 🌟

image

Today we're announcing SpacetimeDB! SpacetimeDB 2.0 has some big changes, so buckle up! Get ready for web development at the speed of light!

To find out in detail how to update your applications for 2.0 see our Migration Guide.

TypeScript/JavaScript Support

In October we launched beta support for TypeScript and JavaScript, and we're happy to announce that with the release of 2.0 TypeScript support is leaving beta! We also have a bunch of updates to the API that being much needed consistency to the APIs.

Web framework integration

Along with TypeScript and JavaScript support, we've built integrations and templates with all your favorite frameworks including:

Unreal Engine/C++ Support

For all those who have been waiting for official Unreal Engine 5 support, it's here! Alongside C++ modules as well!

Incredible performance

SpacetimeDB 2.0 delivers eye watering throughput even for tiny transactions with high contention. Well over 100k transactions per second for TypeScript modules and up to 170k transactions per second for Rust modules!

image

See how it compares to other databases in our new keynote presentation!

A new Maincloud FREE tier and all new pricing!

With 2.0, we're also announcing a brand new, simpler pricing scheme along with a free tier for users who want to try out Maincloud!

This new simplified pricing makes it easier than ever to predict your costs. Check out our pricing calculator on the pricing page.

Spacerace Referral Program

Alongside our new pricing, we're introducing the Spacerace Referral Program where you can get up to 400x more free credits per month by referring friends to the platform.

image

Procedures and HTTP calls

With 2.0 your SpacetimeDB modules are getting a big boost in capability too. For the first time, your modules can now access the outside world with Procedure Functions. Procedure functions give you the ability to make HTTP calls from within your module, letting you integrate directly with external APIs. This is how easy it is to call ChatGPT's API from within your module:

export const ask_ai = spacetimedb.procedure(
  { prompt: t.string(), apiKey: t.string() },
  t.string(),
  (ctx, { prompt, apiKey }) => {
    // Make the HTTP request to OpenAI
    const response = ctx.http.fetch('https://api.openai.com/v1/chat/completions', {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
        'Authorization': `Bearer ${apiKey}`,
      },
      body: JSON.stringify({
        model: 'gpt-4',
        messages: [{ role: 'user', content: prompt }],
      }),
      // Give it some time to think
      timeout: TimeDuration.fromMillis(3000),
    });

    if (response.status !== 200) {
      throw new SenderError(`API returned status ${response.status}`);
    }

    const data = response.json();
    const aiResponse = data.choices?.[0]?.message?.content;

    if (!aiResponse) {
      throw new SenderError('Failed to parse AI response');
    }

    // Store the conversation in the database
    ctx.withTx(txCtx => {
      txCtx.db.aiMessage.insert({
        user: txCtx.sender,
        prompt,
        response: aiResponse,
        createdAt: txCtx.timestamp,
      });
    });

    return aiResponse;
  }

Read more about Procedure Functions.

SpacetimeAuth (and Clerk and Auth0)

And to help you avoid needing to set up additional sidecars and services alongside SpacetimeDB we've also introduced SpacetimeAuth, our first party auth solution. SpacetimeAuth is completely free to use with SpacetimeDB Maincloud!

We've also built tutorials for how to integrate with other auth providers like Clerk and Auth0!

View Functions

In SpacetimeDB 2.0, adding sophisticated read permissions to expose portions of your data to users is as simple as creating a function:

export const players_for_level = spacetimedb.anonymousView(
   { name: 'players_for_level', public: true },
   t.array(playerAndLevelRow),
   (ctx) => {
       const out: Array<{ id: bigint; name: string; level: bigint }> = [];
       for (const playerLevel of ctx.db.playerLevels.level.filter(2n)) {
           const p = ctx.db.players.id.find(playerLevel.player_id);
           if (p) out.push({ id: p.id, name: p.name, level: playerLevel.level });
       }
       return out;
   }
);

You can think of view functions as a table that is backed by a reducer. From the client, they look just like any other table in your database, but in the module they're represented as a function that returns rows that you want to expose to clients. Better yet, the table is automatically parameterized by the identity of the viewing client, allowing different clients to see different data when viewing the same table.

Views can also return custom types allowing you to not only filter rows, but also columns. Views are an elegant way of solving read permissions without introducing a single new concept!

Read more about View Functions.

Typed Query Builder

In SpacetimeDB 2.0, you can kiss your stringly-typed queries goodbye! With our 2.0 SDK and code generation, we generate beautifully typed query builder APIs that allows your clients to build arbitrary queries over the data.

ctx.subscriptionBuilder().subscribe([tables.user.where(user => user.name.eq("Tyler")), tables.message]);

Never worry about runtime errors with your queries again! And the strongly typed queries also help LLMs succeed more often as well.

Even better, you can access this same query builder API inside your view functions to return queries from your views so they can be optimized by our incremental evaluation query engine!

export const high_scorers = spacetimedb.anonymousView(
  { name: 'high_scorers', public: true },
  t.array(players.rowType),
  (ctx) => {
    return ctx.from.players
      .where(p => p.score.gte(1000n))
      .where(p => p.name.ne('BOT'));
  }
);

Event Tables

Event tables are also all new in SpacetimeDB 2.0. Event tables allow you to publish short lived event information to clients without needing to clean up your tables later on. Event tables act like regular tables, but the rows are automatically deleted by SpacetimeDB at the end of a transaction. This both saves you storage costs and also bandwidth, as the database needs to synchronize less state!

Publishing an event to clients is as simple as inserting into a row into the event table, and subscribing to it like any other table.

// server
const damageEvent = table({
  public: true,
  event: true,
}, {
  entity_id: t.identity(),
  damage: t.u32(),
  source: t.string(),
});

export const attack = spacetimedb.reducer(
  { target_id: t.identity(), damage: t.u32() },
  (ctx, { target_id, damage }) => {
    // Game logic...

    // Publish the event
    ctx.db.damageEvent.insert({
      entity_id: target_id,
      damage,
      source: "melee_attack",
    });
  }
);

// client
conn.db.damageEvent.onInsert((ctx, event) => {
  console.log(`Entity ${event.entityId} took ${event.damage} damage from ${event.source}`);
});

Read more about Event Tables.

spacetime.json configuration

With 2.0, we're also introducing a new config file to make it easier to interact with your databases. Now with spacetime.json you can save all your database configuration in a single file that you check in to git, so instead of this:

spacetime generate --lang typescript --out-dir src/module_bindings
spacetime publish --server maincloud --module-path spacetimedb my-database

You can now just type this:

spacetime generate
spacetime publish

spacetime dev

Development is getting simpler too, with our new spacetime dev command. This command is your one stop shop for development. It:

  1. Watches for changes in your module code
  2. Compiles your module
  3. Generates your client module bindings
  4. Publishes your module
  5. Runs your client

Now all you have to do is change your code and your whole app updates instantly!

All new dashboard and metrics

We've also added beautiful new dashboards and analytics so you can monitor your apps and data in real-time! And they update in real-time too! It's incredible to see tables updating live, trust us!

Better LLM tools and benchm...

Read more

Contributors

drogus, kim, and 20 other contributors
Loading

Release v1.12.0 - Client-side Typed Query Builder

04 Feb 17:18
@jdetter jdetter
v1.12.0
92fdc93

Choose a tag to compare

View all tags
Release v1.12.0 - Client-side Typed Query Builder

The end of 1.0 is nigh! 🤩

v1.12 will be the last minor version before we drop SpacetimeDB 2.0! SpacetimeDB 2.0 will come with code breaking changes (you may need to change your modules and clients), but it will not require a migration of the existing data directory, and include backwards compatibility with existing clients and modules, so all existing databases and modules will continue working on both Standalone deploys and Maincloud.

If you're not subscribed to our YouTube channel, you should be. Trust me on that one.

We've got some great updates today in v1.12!

Typed Query Builder

  • Added a typed query builder for the TypeScript client. (#4021)
  • Added a Rust client query builder. (#4003)
  • Added a typed query builder for the C# client, plus additional regression coverage. (#3982, #4123)

You can now subscribe to your server's data with type safe queries from clients:

TypeScript

import { queries } from "./module_bindings";
conn.subscriptionBuilder().subscribe([queries.user.build()]);

C#

conn.SubscriptionBuilder().AddQuery(ctx => ctx.From.User().Build()).Subscribe();

Rust

conn.subscription_builder().add_query(|ctx| ctx.from.user().build()).subscribe();

NOTE: We would like to remove the .build() for 2.0, but you can try it out with the existing API.

Other highlights

  • New front-end framework SDKs

    • Added a Vue framework SDK. (#4037)
    • Added a Svelte framework integration. (#4063)

  • Organizations support

    • Introduced Organizations support. (#4087)

  • Operational tooling improvements

    • Added spacetime login --no-browser for headless/CI environments. (#4142)
    • Core: added a method to query the replica IDs managed by the host controller. (#4160)

Developer experience & docs

  • Added new authentication tutorials:
  • Documentation updates and clarifications, including explaining “maincloud” context. (#4029, #4071, #4168)

Performance & internal improvements

  • Multiple datastore and update-path optimizations (construction, view evaluation fast paths, layout usage, and small data-structure refinements). (#4133, #4134, #4138, #4136)
  • Reduced JS worker request/reply sizes and improved data-structure choices for better cache efficiency. (#4150, #4151)

Reliability & correctness

  • Fixed Hash indices not working. (#4060)
  • Durability: notify waiters after lockfile drop. (#4051)
  • Fixed occasional panic when a client disconnects. (#4162)
  • Improved blob handling flexibility (copy_filter and related). (#4096)
  • Marked MutTxId as !Send to avoid incorrect cross-thread usage. (#4039)
  • Added support and filtering improvements around Uuid (including React Hook where support and making the new Uuid type filterable). (#4030, #3991)

New contributors

What's Changed

Read more

Contributors

drogus, kim, and 17 other contributors
Loading

Release v1.11.3 - Bug fixes + Performance improvements

15 Jan 16:38
@jdetter jdetter
v1.11.3
0244973
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Release v1.11.3 - Bug fixes + Performance improvements

We've got another one for you! A bunch of small fixes including a critical feature to spacetime dev.

spacetime dev

spacetime dev now gets an additional --template argument, just like spacetime init. This allows you to quickly get started with SpacetimeDB on the CLI.

Bug Fixes & Improvements

  • Many small improvements for C# and Unreal.

What's Changed

  • Additional Hex parsing checks to ConnectionId and Identity by @rekhoff in #3988
  • Fix C# null string serialization error + add regression coverage for Issue #3960 by @rekhoff in #3967
  • Update 00300-rust.md by @cloutiertyler in #3943
  • Clarify Windows installation instructions in README by @dejaime in #3923
  • Combine table and index attributes in Rust example by @kistz in #3948
  • CI - LLM benchmark update uses clockworklabs-bot by @bfops in #3998
  • fix(codegen): Initialize UPROPERTY fields in generated Unreal C++ code by @brougkr in #3990
  • CI - LLM benchmark update uses clockwork-labs-bot by @bfops in #4004
  • Fix link to Blackholio demo in Unreal tutorial and update project structure in README by @homersimpsons in #3994
  • Misc docs and small CLI improvements by @cloutiertyler in #3953
  • CI - Decrease number of iterations for long-running UUID test by @bfops in #4014
  • deadlock fix: Make procedure tx abis synchronous by @Shubham8287 in #3968
  • Fixed SERVER_MSG_COMPRESSION_TAG_* descriptions by @egormanga in #4018
  • Provide a common Index trait & simplify and shrink TableIndex by @Centril in #3973
  • --feature no-core-pinning disables core pinning by @Centril in #3983
  • Time out database shutdown by @kim in #4019
  • Unreal SDK failing to handle fragmented messages by @JasonAtClockwork in #4002
  • fix(codegen/unreal): eliminate UObject memory leak in reducer event handlers by @brougkr in #3987
  • Fixes basic issues using the basic-react template. by @cloutiertyler in #4017
  • CI - "Fix" v8 error in TypeScript CI by @bfops in #4022
  • Add error handling for ranged seeks on non-range compat indices by @Centril in #3974
  • Make Uuid Nameable by @kistz in #4011
  • Docs - insert -> try_insert by @bfops in #4025
  • CI - Fix /update-llm-benchmark getting cancelled by @bfops in #4027
  • Add Hash indices by @Centril in #3976
  • Update authentication docs by @JulienLavocat in #4020
  • Despecialize direct indices with too large values into B-Tree indices by @Centril in #3978
  • Expand doc comment on FilterableValue with requirements to implement by @gefjon in #4024
  • Build all of the typescript templates in CI by @jsdt in #3980
  • Move Bound struct out of SpacetimeDB.Internal to SpacetimeDB and Local out of SpacetiemDB.Runtime by @rekhoff in #3996
  • Add Unreal Result type to support C++ and Blueprint by @JasonAtClockwork in #3834
  • Enable RefOption returns from Views to support Views returning a single class by @rekhoff in #3964
  • Version bump to 1.11.3 by @jdetter in #4041
  • Fix logic for ipv6 connections in is_port_available by @jdetter in #4005
  • docs: Add confirmed reads configuration to SDK reference docs by @kim in #4036
  • Add a feature flag no-job-core-pinning by @Centril in #4046
  • docs: fix incorrect dirName for authentication sidebar by @JulienLavocat in #4047

New Contributors

Full Changelog: v1.11.2...v1.11.3

Contributors

kim, bfops, and 14 other contributors
Loading

Release v1.11.2 - Bug fixes + Performance improvements

09 Jan 22:16
@jdetter jdetter
v1.11.2
d53573c

Choose a tag to compare

View all tags
Release v1.11.2 - Bug fixes + Performance improvements

Hello again everyone! We have another release with more improvements.

Host

  • A bunch of performance improvements related to optimizing small transactions and the time between transactions
  • A critical deadlock fix
  • Many small fixes

C#

  • Procedures in C# are here! You can try them out now, but they're not documented, you can see an example usage here. They'll be in beta until 1.12. Please let us know if you run into issues if you try them out.

Typescript

  • A performance improvement to use a new ABI function for faster index lookups

Unreal

  • Several bug fixes submitted by @KirstenWF! Thank you for the contributions.

New /templates directory for sharing templates

  • We've consolidated our various projects and templates into the /templates directory in the repository. We'll be adding many more templates as we go. If you want to use a template you can install one with:
spacetime init --template <the-template-name> # or
spacetime dev --template <the-template-name>

What's Changed

New Contributors

Full Changelog: v1.11.1...v1.11.2

Contributors

drogus, kim, and 16 other contributors
Loading

Release v1.11.1 - Bug Fixes + Performance Improvements

18 Dec 21:23
@jdetter jdetter
v1.11.1
bbfa851

Choose a tag to compare

View all tags
Release v1.11.1 - Bug Fixes + Performance Improvements

Hello again everyone! This is likely going to be our last release before the holidays. We will potentially have one more release before the end of the year but for now we hope you are all happy with these improvements 🙂

Typescript

This release includes several bug fixes and performance improvements related to Typescript:

  • SpacetimeDB now processes sourcemaps included in Typescript modules, so stacktraces in both new and existing modules now show the filenames and line numbers from your source code, not from the bundled JS file.
  • The UTF-8 processing of the TextEncoder and TextDecoder classes is now implemented in native code, meaning string de/serialization will now have less overhead.
  • useTable in a React client now works when specifying columns with camelcase names.
  • Generated client code is now compatible with the noImplicitOverride Typescript configuration option.

What's Changed

Full Changelog: v1.11.0...v1.11.1

⛄ 🎄 🎁 Happy Holidays everyone! 🎁 🎄 ⛄

Contributors

kim, bfops, and 11 other contributors
Loading

Release v1.11.0 - Typed Query Builder

09 Dec 13:35
@jdetter jdetter
v1.11.0
49ccb7a

Choose a tag to compare

View all tags
Release v1.11.0 - Typed Query Builder

Today we've released query builders for Rust and TypeScript modules. The purpose of the query builder API is so that you can write views that will take advantage of the unique performance guarantees of SpacetimeDB's query engine, particularly for realtime subscription updates.

The query builder also now allows you to iterate or scan a table in a view, something that previously wasn't possible using only the index accessors exposed by ViewContext and AnonymousViewContext.

The query builder exposes the following query operators:

  • .where()
    Used for filtering. Equivalent to a WHERE condition in SQL.
  • .leftSemijoin()
    Equivalent to an inner join in sql where a row is return from the lhs only if it matches with a row on the rhs.
  • .rightSemijoin()
    Equivalent to an inner join in sql where a row is return from the rhs only if it matches with a row on the lhs.

Examples (Rust)

use spacetimedb::{Identity, Query, Table, ViewContext, AnonymousViewContext};

#[spacetimedb::table(name = player_state)]
pub struct PlayerState {
    #[unique]
    player_id: u64,
    online: bool,
}

#[spacetimedb::table(name = player_internal)]
pub struct Player {
    #[auto_inc]
    #[primary_key]
    id: u64,
    #[unique]
    identity: Identity,
    name: String,
    #[index(btree)]
    age: u8,
}

#[spacetimedb::table(name = moderator_internal)]
pub struct Moderator {
    #[unique]
    player_id: u64,
}

/// Returns all players.
/// Equivalent to `SELECT * FROM player_internal`.
#[spacetimedb::view(name = player, public)]
fn player(ctx: &AnonymousViewContext) -> Query<Player> {
    ctx.from.player_internal().build()
}

/// Returns the caller's player.
/// Equivalent to `SELECT * FROM player_internal WHERE "identity" = :sender`.
#[spacetimedb::view(name = my_player, public)]
fn my_player(ctx: &ViewContext) -> Query<Player> {
    ctx.from.player_internal().r#where(|p| p.identity.eq(ctx.sender)).build()
}

/// Returns only online players.
/// Equivalent to:
/// ```sql
/// SELECT q.*
/// FROM player_state p JOIN player_internal q ON p.player_id = q.id
/// WHERE p.online
/// ```
#[spacetimedb::view(name = online_player, public)]
fn online_player(ctx: &AnonymousViewContext) -> Query<Player> {
    ctx.from
        .player_state()
        .r#where(|p| p.online.eq(true))
        .right_semijoin(ctx.from.player_internal(), |(p, q)| p.player_id.eq(q.id))
        .build()
}

/// Returns only the caller's player if online.
/// Equivalent to:
/// ```sql
/// SELECT q.*
/// FROM player_state p JOIN player_internal q ON p.player_id = q.id
/// WHERE p.online AND q.identity = :sender
/// ```
#[spacetimedb::view(name = my_online_player, public)]
fn my_online_player(ctx: &ViewContext) -> Query<Player> {
    ctx.from
        .player_state()
        .r#where(|p| p.online.eq(true))
        .right_semijoin(ctx.from.player_internal(), |(p, q)| p.player_id.eq(q.id))
        .r#where(|p| p.identity.eq(ctx.sender))
        .build()
}

/// Returns the moderators.
/// Equivalent to:
/// ```sql
/// SELECT p.* FROM player_internal p JOIN moderator_internal m ON p.id = m.player_id
/// ```
#[spacetimedb::view(name = moderator, public)]
fn moderator(ctx: &AnonymousViewContext) -> Query<Player> {
    ctx.from
        .player_internal()
        .left_semijoin(ctx.from.moderator_internal(), |(p, m)| p.id.eq(m.player_id))
        .build()
}

Examples (TypeScript)

import { schema, table, t, type RowObj } from 'spacetimedb/server';

const playerState = table('playerState', {
  playerId: t.u64().unique(),
  online: t.bool(),
});

const playerInternal = table('playerInternal', {
  id: t.u64().primaryKey().autoInc(),
  identity: t.identity().unique(),
  name: t.string(),
  age: t.u8().index('btree'),
});

const spacetimedb = schema(playerState, playerInternal);

spacetimedb.view(
  { name: 'my_online_player', public: true },
  t.array(playerInternal.row()),
  ctx => {
    return ctx.from.playerState
      .where(p => p.online.eq(true))
      .rightSemijoin(ctx.from.playerInternal, (p, q) => p.playerId.eq(q.id))
      .where(p => p.identity.eq(ctx.sender))
      .build();
  }
);

Bug Fixes

  • Fixes an issue with the --delete-data=on-conflict flag of spacetimedb publish
  • Fixes an issue where databases were returning 400/500 errors after publishing with -c
  • Fixes an issue where on_insert and on_delete were not firing correctly for per-client (ViewContext) views

What's Changed

New Contributors

Full Changelog: v1.10.0...v1.11.0

Contributors

drogus, kim, and 15 other contributors
Loading

Release v1.10.0 - Procedures and HTTP Requests

27 Nov 04:42
@jdetter jdetter
v1.10.0
1d576dc

Choose a tag to compare

View all tags
Release v1.10.0 - Procedures and HTTP Requests

Today we have an absolute game changer for SpacetimeDB. SpacetimeDB 1.10 introduces the ability for databases to perform HTTP requests to external services right from within your module! This is one of our most-requested features, and we're very excited to share it with you all.

SpacetimeDB Reducers are extremely powerful. They are atomic, transactional, pure, retryable, and replayable. The challenge was: in order to maintain these properties and guarantees, they need to be isolated from the outside world and can't be allowed to cause any observable side effects.

However, HTTP requests are inherently side-effecting, and are too useful not to have. It turns out the solution is pretty simple: keep reducers side effect free, and introduce a new kind of database function with weaker guarantees and more powers. Enter a new type of SpacetimeDB function: Procedures.

Examples

Just like a reducer, a procedure is a function defined in your module which runs inside the database. Unlike a reducer, procedures don't correspond 1-to-1 with transactions. Instead, you explicitly manage transactions inside the body of your procedure:

#[spacetimedb::procedure]
fn find_highest_level_player(ctx: &mut ProcedureContext) {
    let highest_level_player = ctx.with_tx(|ctx| {
        ctx.db.player().iter().max_by_key(|player| player.level)
    });
    match highest_level_player {
        Some(player) => log::info!("Congratulations to {}", player.id),
        None => log::warn!("No players..."),
    }
}

Being able to run code in the database without a transaction opens a lot of possibilities for new APIs we could expose. The first of these, releasing today, is HTTP requests:

#[spacetimedb::procedure]
fn get_request(ctx: &mut ProcedureContext) {
    match ctx.http.get("https://example.invalid") {
        Ok(response) => {
            let (response, body) = response.into_parts();
            log::info!(
                "Got response with status {} and body {}",
                response.status,
                body.into_string_lossy(),
            )
        },
        Err(error) => log::error!("Request failed: {error:?}"),
    }
}

Take a look at the documentation on the new procedure APIs for more details,
and join us on Discord to let us know what other side effects you want APIs for!

As of this release, only Rust and TypeScript modules can define procedures. We're hard at work adding support to C# modules, and will be releasing them soon. We'll also be cleaning up the new APIs in response to your feedback, so for now procedures are unstable and subject to breaking changes.

TypeScript fixes

In this release, we've also fixed quite a few issues which were reported in the new TypeScript SDK.

  • This issue by exporting the SubscriptionHandle type with the REMOTE_MODULE type applied.
  • This issue by converting to camelCase for column names in code generation.
  • Fixes an issue where onMyReducer callbacks were passing arguments as variadic params, while the types indicated they would be passed as an object. onMyReducer((ctx, argA, argB, argC) => {}) vs onMyReducer((ctx, { argA, argB, argC}) => {})`
  • Fixes an issue where the table type name was used instead of the table name in code generation for constructing tables.
  • Fixes issue with ScheduleAt being used in non-table types.
  • Fixes issue where template projects do not use the correct lifecycle reducer setup
  • Fixes an issue where .insert() returns incorrect objects
  • Fixes an issue where .update() causes error with .autoInc() field

We intend for TypeScript modules and clients to rapidly approach stability. The most invasive breaking changes have already been made.

What's Changed

New Contributors

Full Changelog: v1.9.0...v1.10.0

Contributors

drogus, bfops, and 10 other contributors
Loading