EfTurso.Data 0.0.1-alpha

<div align="center">

<img src="assets/icon.png" alt="EfTurso" width="96" />

EfTurso

Entity Framework Core 10 provider for Turso / libSQL. Write LINQ, not HTTP.

Keep using DbContext, Include, Where and migrations exactly as you know them. Under the hood, the provider talks to Turso Cloud over the Hrana protocol.

Alpha: this is an early alpha release (0.0.1-alpha). The API may change and it is not recommended for production yet. Feedback and bug reports are very welcome.

Disclaimer: community project, not officially affiliated with Turso. Built independently on the public Hrana protocol spec and the libSQL ecosystem.

</div>

Why this provider

• Familiar. Your existing EF Core code, LINQ queries and migrations work as they do with any other provider.
• Light. No native binaries to ship for the connection: everything goes over HTTPS to your Turso database.
• Reliable by construction. LINQ translation, type mapping and migration SQL are inherited from the Sqlite provider, so they are the same battle-tested code paths. Only the connection layer is new.
• Honest. When a construct can't be translated for Turso, you get a clear exception, not silently wrong SQL.

Contents

• Installation
• Quick Start
• Requirements
• Architecture
• Project Structure
• Branch Flow
• Resources
• Contributing

Installation

dotnet add package EfTurso

Quick Start

using Microsoft.EntityFrameworkCore;
using EfTurso;

var optionsBuilder = new DbContextOptionsBuilder<BlogDbContext>();
optionsBuilder.UseTurso("Server=https://<database>-<organization>.turso.io;Token=<auth-token>");

using var db = new BlogDbContext(optionsBuilder.Options);
await db.Database.EnsureCreatedAsync();

var user = await db.Users
    .Include(u => u.UserDetail)
    .FirstOrDefaultAsync(u => u.Id == 1);

Console.WriteLine(user?.Name ?? "Not found");

public class BlogDbContext : DbContext
{
    public BlogDbContext(DbContextOptions<BlogDbContext> options) : base(options) { }
    public DbSet<User> Users => Set<User>();

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        modelBuilder.Entity<User>(entity =>
        {
            entity.HasKey(e => e.Id);
            entity.HasOne(e => e.UserDetail)
                  .WithOne(e => e.User)
                  .HasForeignKey<UserDetail>(e => e.UserId);
        });
    }
}

Requirements

• .NET 10
• Entity Framework Core 10 (10.0.x). This is the only supported EF Core major version for now; the provider relies on a few EF Core internals that can change between major versions.
• A Turso Cloud database and its auth token

Environment: this project targets Turso Cloud only. A local sqld/Docker workflow is not available yet (tracked in #2). The functional and conformance tests run against a real Turso Cloud database via test/protocol/run-cloud-tests.ps1, which reads credentials from test/protocol/.env and never leaves them set in your shell.

Architecture

This provider takes advantage of the ~99% SQL compatibility between libSQL and SQLite. Instead of reinventing LINQ translation, type mapping and migrations SQL generation, it inherits those layers from Microsoft.EntityFrameworkCore.Sqlite and replaces only the connection/protocol layer via the Hrana protocol over HTTP.

Project Structure

/src
  EfTurso.Data/                        # ADO.NET layer (System.Data.Common)
  EfTurso/          # EF Core provider
/test
  EfTurso.Data.Tests/
  EfTurso.Tests/
  EfTurso.FunctionalTests/

Branch Flow

• master: production/stable, the default branch.
• rc/alpha: release candidate (alpha line).
• dev: integration and development. New work lands here first.

Flow: dev → rc/alpha → master.

Resources

• Turso Documentation
• Hrana Protocol Specification

Contributing

Issues and pull requests are welcome. Please read CONTRIBUTING.md first: it covers the technical scope and the contribution workflow.

License

MIT. See LICENSE.