The Replay app uses different database backends depending on the platform: - **Tauri (desktop)**: SQLite with Drizzle ORM - **Web**: IndexedDB with the `idb` library
Media Type Database
CLI tool to update caniuse-lite to refresh target browsers from Browserslist config
Database layer for Voyant. Drizzle-based schemas for IAM + infra, runtime adapters for edge, serverless, and Node.js, TypeID columns, CRUD factory, and the runtime LinkService.
The schema definition for collections
Traverse JSON Schema passing each schema object to callback
HDI content deployment
webpack Validation Utils
A database implementation that treats JSONL files as tables using SQLite
PostgreSQL schema migration tool with microsharding and clustering support
The ultimate javascript content-type utility.
JSON Schema validation and specifications
FullStack database toolkit with built-in access control and automatic API generation.
Drizzle ORM schema (85 tables) for RevealUI on NeonDB (Postgres). Ships with RevealUI.
Shared Prisma schema for Legal AI applications
Schemas describing various structures used by nyc and istanbuljs
Automatically generate GraphQL schema or customizable schema config fields from Drizzle ORM schema
TypeScript definitions for json-schema
Agents Core contains the database schema, types, and validation schemas for Inkeep Agent Framework, along with core components.
Postgres target pack for Prisma Next
A reactive client store for building super fast apps on sync
JSON Schema TypeScript definitions with complete inline documentation.
A family of specs for interoperable TypeScript
Reactive, Offline-First adapter for TanStack DB using RxDB. Sync, Replication and Local-First support.
YamlDb is a database-independent format for dumping and restoring data. It complements the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work.
DrySQL uses your DB's information schema to identify keys, and generate associations and validations for ActiveRecord objects. You defined the schema on your DB ... don't re-define it in your application code. Legacy DB Tables, Ruby Desktop apps, Rails apps...DrySQL's got all your databases covered
GitLab fork. YamlDb is a database-independent format for dumping and restoring data. It complements the the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work
YamlDb is a database-independent format for dumping and restoring data. It complements the the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work
YamlDb is a database-independent format for dumping and restoring data. It complements the the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work
IronmineYamlDb is a database-independent format for dumping and restoring data. It complements the the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work
YamlDb is a database-independent format for dumping and restoring data. It complements the the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work
YamlDb is a database-independent format for dumping and restoring data. It complements the the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work
YamlDb is a database-independent format for dumping and restoring data. It complements the the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work
YamlDb is a database-independent format for dumping and restoring data. It complements the the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but only for the databases typically used by Rails apps. Users, permissions, schemas, triggers, and other advanced database features are not supported - by design. Any database that has an ActiveRecord adapter should work
ActiveRecordDumper is a fork of YamlDb gem without any explicit Rails dependencies. This way it can be used by any AR-enabled app (e.g. Sinatra) without pulling whole Rails in. YamlDB/ActiveRecordDumper is a database-independent format for dumping and restoring data. It complements the database-independent schema format found in db/schema.rb. The data is saved into db/data.yml. This can be used as a replacement for mysqldump or pg_dump, but it only supports features found in ActiveRecord-based (Rails, etc.) apps. Users, permissions, schemas, triggers, and other advanced database features are not supported by design. Any database that has an ActiveRecord adapter should work.
vdb mounts a self-contained D3-powered entity-relationship diagram at any path in your Rails app. It reads db/schema.rb (and any additional schema files you configure), infers FK relationships, and renders an interactive force-directed graph with search, zoom, drag-to-rearrange, and position persistence. Ships with zero asset-pipeline dependencies — D3 and Stimulus are loaded from CDN. Recommended for development environments only.