docs.rs failed to build sea-orm-turso-0.2.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
sea-orm-turso-0.1.0
sea-orm-turso
A universal SeaORM adapter for Turso Database.
Features
- MVCC: Full multi-version concurrency control via Turso engine
- In-process: No network overhead, runs directly in your application
- Async: Native async/await support via Tokio
- WAL persistence: In-memory speed with file-based durability
- Cloud sync: Optional sync with Turso Cloud (via
turso::sync) - Universal: Works with any SeaORM-based framework (Loco, Axum, etc.)
Installation
[]
= "0.2"
= "2.0"
Quick Start
use TursoConnection;
use ;
async
Integration with Loco
// In your app.rs after_context hook:
use TursoConnection;
async
API
Connection
// Connect to a file
let db = connect.await?;
// Connect to memory (no persistence)
let db = connect_memory.await?;
// From existing Turso database
let db = from_existing;
Usage with SeaORM
The TursoConnection implements SeaORM's ConnectionTrait and TransactionTrait, so it works seamlessly with all SeaORM APIs:
use ;
// Query
let users = find
.filter
.all
.await?;
// Insert
let new_user = ActiveModel ;
new_user.insert.await?;
// Transaction
db.transaction.await?;
Architecture
┌─────────────────────────────┐
│ Your SeaORM Code │
├─────────────────────────────┤
│ TursoConnection │ ← Implements ConnectionTrait
├─────────────────────────────┤
│ Turso Engine (MVCC) │ ← In-process, async, concurrent writes
├─────────────────────────────┤
│ WAL → File Persistence │ ← Survives restarts
└─────────────────────────────┘
License
MIT OR Apache-2.0