This repository has been archived by the owner on Mar 1, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 3
Design config options for mongo-knex #4
Labels
Comments
This was referenced Nov 8, 2018
Closed
NOTE: Expansions (previous aliases) are not forwarded to mongo-knex. The design we need here is for passing the relations. We currently use:
We should think about if this structure also works for other relation types. |
kirrg001
added a commit
that referenced
this issue
Dec 5, 2018
refs #4 - mongo-knex does not know about the aliases/expansions concept - mongo-knex receives a full and ready mongo JSON object - mongo-knex task is it to apply queries to a query builder - mongo-knex task is not to replace values
The naming of variables should def be more consistent e.g.: |
naz
added a commit
to naz/mongo-knex
that referenced
this issue
Dec 7, 2018
naz
added a commit
that referenced
this issue
Dec 7, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
Projects want to use NQL and want to forward information about database tables, in particular database relations.
Goal
Design a config options which makes it possible to query the database based on this config object.
How do we pass the table information to mongo-knex?
Tasks
The text was updated successfully, but these errors were encountered: