lroal

Orange ORM 5.0.0 is out.

Breaking:

- getAll removed; use getMany (same signature).

- getOne no longer accepts filter as first arg; move it to where.

Also:

- ExpressJS before/after hooks for row-level security.

- SQLite user-defined functions.

- Enums support.

I am happy to announce that orange-orm now supports Cloudflare D1. It does not need the node compatability flag. It is a typescript ORM.

The datatable component is pretty advanced. https://primevue.org/datatable/ This also seems more mature than Vuetify.

You should try https://github.com/alfateam/rdb

It is database agnostic. It works with sqlite, mssql, mysql, postgres, oracle, and sapase.

It gives you full intellisense without code generation - even when running pure javascript.

You can run it from the browser in a secure manner, as you can host it in express js via adapter.

I am the author.

You should really try out RDB, an ORM that I've been working on since 2014.

https://rdbjs.org

It has a very small fooprint - well suited for Amazon lambda. We now support client over HTTP (in a safe manner), making it accessible in-browser.

Key Features:

No code generation required

Full intellisense, even when mapping tables and relations

Powerful filtering - with any, all, none at any level deep

Supports JavaScript and TypeScript

ESM and CommonJS compatible

Succint and concise syntax

Works over http

I am excited about this release of RDB. Rich Querying Model Concise API: Developer-friendly & expressive. Full IntelliSense without code generation. TS & JS Ready Browser-Friendly: Build web apps with RDB in Express

The direct link to streaming docs: https://github.com/alfateam/rdb/blob/master/docs/docs.md#_st...

https://github.com/alfateam/rdb/blob/master/docs/docs.md#_st...

Agree

It is not supported today. But it would't be any problem to implement it. Please create an issue if you want it.

My plan was to stick to promises only. Unless there are lots of lots of developers that really wants callbacks.

Rdb (Relational Database) is meant only for Relation Databases (sql). I have no plans on supporting document databases - that would probably a bad compromize. And the api would be affected in a negative way.

Rdb is used in commercial products at my employer Timpex (www.timpex.no). So it will definitely be maintained. The code was initially closed source in csharp, we refined it and released it as OSS in javascript.

It was created because we needed a solution with persistence ignorance and that does not have any constraints on foreign key naming, columns, table and so on. By persistence ignorance I mean not needing to call model.save() or pass the connection around everywhere - just edit the properties and commit the transaction.

Everything in rdb is developed TDD outside-in. So it has a lot of unit tests, but not that many integration tests. There are running examples in the demo repo though that could be considered as kind of integration tests.

Choices against sequelize and bookshelf: that is not my mission. If you want a closer integration with express.js, those orms are a better fit than rdb. My main focus on rdb was to keep the API simple and expose as little of the interior as possible - Tell Dont Ask principle.

How to expect rdb to evolve ? -domain logic -aggregate functions -order by -support sqlLite