Support dynamic schema selection at query time (schema-per-tenant use case)

[soroush]

Hello SeaORM team, first of all thank you for the project, it has been a great experience so far.

This is a duplicate of discussions/2117 with more elaboration. I would like to request support for dynamic schema selection at query time, without baking the schema name into entity definitions.

My setup

I am building a multi-tenant system using PostgreSQL with a schema-per-tenant architecture:

• Each user account gets its own PostgreSQL schema created at runtime (e.g. tenant_12345)
• All schemas share the exact same structure
• The number of schemas is dynamic and unbounded
• Strong tenant isolation is required

From an application perspective:

• The database connection always points to the same database
• The schema is determined per request / per user
• The same set of entities should operate on different schemas

Current limitation

Currently, SeaORM models the schema as part of the entity definition:

#[sea_orm(schema_name = "tenant_1")]

This makes dynamic schemas difficult because:

• Schema names must be known at compile time
• Entities must be duplicated per schema
• Using SET search_path is unsafe with connection pooling
• Raw SQL becomes the only practical option

Requested feature

I would like to be able to:

1. Override the schema at query time, for example:

Entity::find()
    .schema("tenant_123")
    .all(&db)
    .await?;

or:

db.with_schema("tenant_123").find(Entity::find()).await?;

2. Use the same entity definitions regardless of schema name.

3. Optionally enforce schema specification, e.g.:

• A connection mode where queries without an explicit schema are rejected
• Or entities declared as “schema-required”

So that:

• The connection stays on a default schema
• Every query must explicitly specify the tenant schema
• Accidental cross-tenant access is prevented

Thank you for considering this feature.