You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(First please check that this issue is not already solved as described
here)
Tell us what broke. The more detailed the better.
If you can, please create a simple example that reproduces the issue and link to a gist, jsbin, repo, etc.
find will always return records with an id, and while this is often useful, it makes it difficult to customize the query with something like distinct or group by.
There should be a way to remove the id column from a query.
Actual behavior
The id column is included in queries, which is problematic when you want to alter the query with something like distinct as explained in Customizing the query.
System configuration
Module versions (especially the part that's not working):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Apologies if the issue could not be resolved. FeathersJS ecosystem modules are community maintained so there may be a chance that there isn't anybody available to address the issue at the moment. For other ways to get help see here.
Steps to reproduce
(First please check that this issue is not already solved as described
here)
find
will always return records with anid
, and while this is often useful, it makes it difficult to customize the query with something likedistinct
orgroup by
.An example, including a workaround, are available at https://gist.github.com/jordanbtucker/30d403170e3104b841f7195d25ba6101.
Expected behavior
There should be a way to remove the
id
column from a query.Actual behavior
The
id
column is included in queries, which is problematic when you want to alter the query with something likedistinct
as explained in Customizing the query.System configuration
Module versions (especially the part that's not working):
NodeJS version:
v12.18.1
The text was updated successfully, but these errors were encountered: