A light and extensible ORM for Javascript applications.

Goals

• Light. No frills. Frills are the providence of extensions!
• Support server and client-side use.
• Useful, complete, verbose, and evolving documentation.
• Excellent test-suite and code coverage.
• Minimum configuration required, but maximum flexibility allowed.
• Not re-inventing the wheel. Capitalize on common libraries without introducing bloat.

Feature Overview

• Primarily ES6, if that matters to you. Certain Javascript eccentricities make it difficult to define models using ES6 syntax, otherwise, everything should be ES6.
• AST-based queries for extensibility
• Supports typical relations (one-to-many, many-to-one, one-to-one, many-to-many)
• Supports many-to-many with custom bridge tables
• Supports custom foreign key definitions

Installation

One ORM Core is not intended for direct installation. It doesn't really serve a purpose beyond underpinning the extensions that use it. That said, installation is easily accomplished via NPM:

npm i one-orm-core

Usage

One ORM Core is not intended to be used directly. Extensions rely on core to handle model management and AST generation, but core does not perform communication with underlying datastores on its own. That said, if you wish to understand how core works, please see SPECIFICATION.

Contribute

See CONTRIBUTING.

Change Log

See CHANGELOG.

Licence

MIT Licensed. See LICENSE.

Authors

Thomas P. Wilson created One ORM.

Andrew Hartwig named One ORM.

Trevor Delamorandiere was really stoked about One ORM.

These fine people have brought One ORM closer to becoming the One ORM to rule them all!