-
Notifications
You must be signed in to change notification settings - Fork 4.4k
🐛 Bug Report: select query in a relationship database #5880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
HI |
Hi @monofactory shall I close this issue if no additional help is required here? |
Hey @monofactory, is this still an issue for you in 1.4.x? If so, are you able to add the appwrite container logs here? |
hey @monofactory I am pretty sure, This should work... |
I wanted to chime in on this, as it relates to the FR I opened #7033 . I'm affected by the same issue. But, this is not a bug, this is an FR as the documentation and code states that the features required to resolve this need are potentially planned for a future release.
I don't know if there is a place to track planned features like this one. And as I've spent some time looking through the code for Appwrite and Utopia Database, I'd be willing to contribute code changes to both or either this issue and/or my interim FR. |
+1 For query support for relationships. I have a use case where I would love to have the ability to only have certain fields return for related documents. |
👟 Reproduction steps
Query.select([
"title",
"category",
"imageLinks",
"uid",
...
"users.*" // relationship collection "users" All of the user's data is imported
]),
👍 Expected behavior
Query.select([
"title",
"category",
"imageLinks",
"uid",
...
"users.name" // Only the data I want ==> not working
]),
👎 Actual Behavior
AppwriteException: general_unknown, Server Error (500), #0 ClientMixin.prepareResponse (package:appwrite/src/client_mixin.dart:73:9)
#1 ClientIO.call (package:appwrite/src/client_io.dart:373:14)
🎲 Appwrite version
Version 1.3.x
💻 Operating system
MacOS
🧱 Your Environment
appwrite 1.3.8
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: