Limitations, Missing Functionality, and Known Issues

This page is for listing the current limitations and known issues with ts-pg-orm.

Missing Functionality

1. No support for transactions.
2. For many-to-many relations, a join table store is created for these to create and delete rows, however as of writing (v4.1) they are currently quite simple, with only create and delete functionality.
3. When one has a many-to-many-to-many relation structure (for example, this is usually found in user <-> user group <-> permission systems), get and getMany don't have an ability to traverse the intermediate (e.g. user group) data format and, for example, "find all of the permissions of a user". This requires complexity that would be undesirable. Currently, this SQL must be manually created using the type-enforced SQL info that is available for your data formats.

Limitations

1. get and getMany are limited to 3 levels of related data nesting for the Typescript compiler [0]. Deeper nesting will still execute nominally as Javascript, but the Typescript linting will fail (i.e. complain) beyond 3 levels.

[0] This is due to performance issues that the Typescript compiler typically has with complex recursive types.