Crate spanner_rs[][src]

Expand description

An asynchronous client for the Cloud Spanner database.

Example

use spanner_rs::{Client, Error};

#[tokio::main]
fn main() -> Result<(), Error> {
    let mut client = Client::configure()
        .project("my-gcp-project")
        .instance("my-instance")
        .database("my-database")
        .connect()
        .await?;

    // assuming the following table:
    //   person(id INT64, name STRING(MAX), data BYTES(MAX))
    client
        .read_write()
        .run(|tx| {
            tx.execute_update(
                "INSERT INTO person(id, name, data) VALUES(@id, @name, NULL)",
                &[("id", &42), ("name", &"ferris")],
            )
        })
        .await?;

    let result_set = client
        .read_only()
        .execute_sql("SELECT * FROM person", &[])
        .await?;

    for row in result_set.iter() {
        let id: u32 = row.get_by_name("id")?;
        let name: &str = row.get_by_name("name")?;
        let data: Option<&[u8]> = row.get_by_name("data")?;

        println!("found person: {} {} {:?}", id, name, data);
    }

    Ok(())
}

Transactions

Cloud Spanner supports several transaction “modes”:

  • read-only: provides guaranteed consistency between several reads, cannot write;
  • read-write: the only way to write into Cloud Spanner they use a combination of locking and retries and are typically more expensive;
  • partitioned DML: these are unsupported by this client at the moment.

Read Only

Reads are done within “single-use” transactions and can be bounded to determine what data is visible to them, see TimestampBound. Reading is done using ReadContext which can be obtained using Client::read_only() or Client::read_only_with_bound().

Example

let result_set = client
    .read_only()
    .execute_sql("SELECT COUNT(*) AS people FROM person", &[])
    .await?;
let people: u32 = result_set.iter().next().unwrap().get_by_name("people")?;

Read Write

Read / write transactions are done through TransactionContext which extends ReadContext to allow writes. When a transaction that conflicts with another tries to commit, Cloud Spanner will reject one of them let the client know it may retry. This client encapsulates the necessary retry logic such that applications do not need to implement it themselves.

Example:

client.read_write().run(|tx| {
    // this closure may be invoked more than once
    Box::pin(async move {
        // read
        let rs = tx.execute_sql("...", &[]).await?;
        // write
        tx.execute_update("...", &[]).await?;
    })
})

Structs

An asynchronous Cloud Spanner client.

Configuration for building a Client.

Builder for Config.

Allows running read/write transactions against Cloud Spanner.

Enums

Specifies the bounds withing wich to make reads in Spanner.

Traits

Defines the interface to read data out of Cloud Spanner.

Defines the interface to read from and write into Cloud Spanner.