sea-orm-cubrid

SeaORM backend crate for CUBRID via SeaORM's ProxyDatabaseTrait.

Installation

[dependencies]
sea-orm = { version = "1", features = ["proxy"] }
sea-orm-cubrid = "0.1"

Quick Start

use sea_orm::{EntityTrait, DbErr};

#[tokio::main]
async fn main() -> Result<(), DbErr> {
    let db = sea_orm_cubrid::connect("cubrid://dba:@localhost:33000/demodb").await?;

    // Use SeaORM as usual.
    // let models = cake::Entity::find().all(&db).await?;

    db.ping().await?;
    Ok(())
}

Architecture

sea-orm-cubrid does not fork SeaORM. It adapts cubrid-tokio into SeaORM's proxy backend.

flowchart TD
    A[Application] --> B[SeaORM]
    B --> C[sea-orm-cubrid\nProxyDatabaseTrait]
    C --> D[cubrid-client\nSync Client]
    D --> E[CAS Protocol]
    E --> F[CUBRID Server]

    C -. async to sync bridge via spawn_blocking .-> D

Loading

sequenceDiagram
    participant App as Application
    participant ORM as SeaORM (async)
    participant Proxy as sea-orm-cubrid (ProxyDatabaseTrait)
    participant Client as cubrid-client (sync)
    participant CAS as CAS Protocol
    participant DB as CUBRID Server

    App->>ORM: Entity/query API call
    ORM->>Proxy: execute/query with Statement
    Proxy->>Proxy: spawn_blocking delegation
    Proxy->>Client: sync execute/query
    Client->>CAS: wire protocol request
    CAS->>DB: brokered SQL execution
    DB-->>CAS: result set / status
    CAS-->>Client: protocol response
    Client-->>Proxy: rows / affected count
    Proxy-->>ORM: ProxyRow / ExecResult
    ORM-->>App: async result

Loading

• SeaORM SQL generation uses DbBackend::MySql for CUBRID-compatible SQL.
• CubridProxy converts Statement values and query result rows.
• tokio::sync::Mutex protects shared async client state.

Type Mapping

SeaQuery Value	CUBRID protocol Value	Notes
Bool(Some(v))	Bool(v)	CUBRID stores BOOLEAN semantics over integer types
Int(Some(v))	Int(v)	direct
BigInt(Some(v))	Long(v)	direct
Float(Some(v))	Float(v)	direct
Double(Some(v))	Double(v)	direct
String(Some(v))	String(v)	direct
Bytes(Some(v))	Bytes(v)	direct
null variants	Null	mapped to protocol null

CUBRID Limitations

• No RETURNING support on DML statements
• No native JSON type
• No native BOOLEAN type (modeled via numeric values)

FAQ

Why does this use DbBackend::MySql?

SeaORM and SeaQuery already provide robust MySQL SQL generation, which is the closest backend family to CUBRID syntax for common ORM operations.

Do I need a patched SeaORM?

No. This crate uses the public proxy extension pattern from SeaORM.

Does this crate include live-database tests?

No. Test coverage is offline and deterministic.

Roadmap

See ROADMAP.md for this project's direction and next milestones.

For the ecosystem-wide view, see the CUBRID Labs Ecosystem Roadmap and Project Board.

Ecosystem

Package	Description
cubrid-rs	Native Rust driver (sync + async)
sea-orm-cubrid	SeaORM backend for CUBRID (this package)