Access to native commands #14

New issue

Open

opened 2026-08-07 15:23:54 +02:00 by c.fahner · 0 comments

c.fahner commented

2026-08-07 15:23:54 +02:00

Owner

Currently the ORM has no way to work around its limitations. By definition an ORM is always playing catch-up with database features or optimizations.

Collections should (optionally) be able to implement an interface that allows executing native commands (which could be cursor-based, a WriteCommand or a generic Command).

This interface should also expose a unique database identifier to allow remaining compatible with multiple databases. This identifier should be checked before sending any command to avoid allocating multiple commands in-memory of which at most one will be used.

The interface has to be optional as it does not make sense for every implementation (such as the in-memory implementation).

Currently the ORM has no way to work around its limitations. By definition an ORM is always playing catch-up with database features or optimizations. Collections should (optionally) be able to implement an interface that allows executing native commands (which could be cursor-based, a `WriteCommand` or a generic `Command`). This interface should also expose a unique database identifier to allow remaining compatible with multiple databases. This identifier should be checked before sending any command to avoid allocating multiple commands in-memory of which at most one will be used. The interface has to be optional as it does not make sense for every implementation (such as the in-memory implementation).

c.fahner added the

Kind/Feature

label

2026-08-07 15:23:54 +02:00