8000 post-1.0: expose PreparedQuery over UniFFI · Issue #181 · project-minigraf/minigraf · GitHub
[go: up one dir, main page]

Skip to content

post-1.0: expose PreparedQuery over UniFFI #181

Closed

Description

@adityamukho

Roadmap source

ROADMAP.md: Phase 8.2, "Post-1.0 FFI deferrals".

Work item

Expose prepare() / PreparedQuery through the UniFFI-based bindings.

Context

Prepared statements require a stateful handle and bind-slot substitution across the FFI boundary. The design was deferred until the basic FFI API had proven stable.

Acceptance criteria

  • Add a stable FFI handle for prepared queries.
  • Support the existing bind value types exposed by Rust prepared statements.
  • Add FFI tests covering repeated execution with different bindings.
  • Document handle ownership and error behavior.

Activity

  1. added
    enhancementNew feature or request
    rustPull requests that update rust code
    on May 1, 2026
  2. added this to the 2.0 milestone on May 17, 2026
  3. modified the milestones: v3.0.0, v3.1.0 on Sep 26, 2026
  4. modified the milestones: v3.1.0, v3.0.0 on Oct 9, 2026
  5. adityamukho commented on Oct 24, 2026

    @adityamukho
    CollaboratorAuthor

    Done on v3, in every binding:

    Spec docs/superpowers/specs/2026-10-24-prepared-query-ffi-design.md, plan docs/superpowers/plans/2026-10-24-181-prepared-ffi.md. Follow-ups filed: minigraf-node#17, minigraf-c#10 (an open cursor or fact log keeps the file registered across close()). The binding pins stay at 5f2ba46e until #316's binding work adds a set value form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestrustPull requests that update rust code

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0