Big fan of what you've built — the schema designer, ER diagrams, cascade simulator, and Drizzle integration are exactly the CF-native admin tools I've been looking for.
I'm porting a multi-party app from Airtable + Vercel Blob to D1 + R2. The data plane ports cleanly: HTTP+JSON+blobs+token-auth maps 1:1, schema control is better, no rate limits, no seat tax, public R2 URLs replace Airtable attachment URLs. The one thing I don't see a clear answer for is end-user row editing — non-technical users (architects, fabrication operators, contractors) clicking a cell and typing a value.
Before forking, I wanted to ask if this is aligned with your direction.
Concretely missing (from the README — couldn't verify against the live demo since it's behind Access):
- Inline click-to-edit cells with field-type-aware inputs (date pickers, dropdowns from CHECK constraints / FK lookups, file picker for R2 attachment columns)
- Column-header sort
- Predicate filters (operator + value, not just "contains")
- Attachment/image rendering for blob URL columns
The data layer is already there — introspection, schema metadata, query execution. Layering TanStack Table or AG Grid on top as the edit overlay feels additive rather than disruptive.
Two questions:
- Is end-user-facing row editing aligned with the project's direction, or is d1-manager intentionally an admin/DBA tool?
- If it's in scope, do you have preferences on table library, save model (optimistic vs server-confirmed), and the RBAC story for separating admin vs end-user contexts?
Happy to scope a focused PR if you'd accept it. Either way, thanks for the work — closest thing I've found to a CF-native answer for what Airtable does.
Big fan of what you've built — the schema designer, ER diagrams, cascade simulator, and Drizzle integration are exactly the CF-native admin tools I've been looking for.
I'm porting a multi-party app from Airtable + Vercel Blob to D1 + R2. The data plane ports cleanly: HTTP+JSON+blobs+token-auth maps 1:1, schema control is better, no rate limits, no seat tax, public R2 URLs replace Airtable attachment URLs. The one thing I don't see a clear answer for is end-user row editing — non-technical users (architects, fabrication operators, contractors) clicking a cell and typing a value.
Before forking, I wanted to ask if this is aligned with your direction.
Concretely missing (from the README — couldn't verify against the live demo since it's behind Access):
The data layer is already there — introspection, schema metadata, query execution. Layering TanStack Table or AG Grid on top as the edit overlay feels additive rather than disruptive.
Two questions:
Happy to scope a focused PR if you'd accept it. Either way, thanks for the work — closest thing I've found to a CF-native answer for what Airtable does.