-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Enhance query capabilities when using Postgres #2877
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
I'm willing to start working on this but I'm not that well acquainted with the entire codebase. If someone can provide pointers on where to start, what gotchas to be aware of and how not to break the Mongo side of things, it would be very helpful |
I'm not sure we want to focus on having different interfaces depending on the storage engine. Transactions would be nice to ensure consistency during the writes, the distinct value would also work in mongo db through an aggregation. |
Is it currently possible to extend the routes handled by parse server in a manner that would allow the new handlers to use the existing mechanism for authenticating and sanitizing requests? |
That would require to add some 'feature support' mechanisms into the adapters, in order to abstract the support in both adapters. Before going to far ahead with Postgres, I believe we should also solidify the existant code. Some tests are failing in the CI, others are disabled etc... |
In that case, if someone can guide me in implementing one test case, I would hopefully be able to help bring the existing Postgres related code base up to scratch. |
name: 'error', |
With the recent improvement in Postgres support, is it a good time to start a discussion on whether/how to extend parse server to fully utilize the capabilities of Postgres? |
There is still 30 tests that are excluded with PG (6 are also excluded with mongo), maybe we can focus on drilling those down before expanding query capabilities? |
Sure. Are all of these contained in |
and also |
got it. thanks! |
Some won't probably fix, but others could very well fix 'easily' |
One easy trick ton only run those, is to |
Thanks for the tip :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Postgres allows additional types of queries that aren't currently exposed by the database adapter (for example - getting distinct values, executing a transaction, setting a per transaction consistency level and a whole lot more)
It would be great if Parse Server can allow users to execute queries such as these when used with Postgres.
The text was updated successfully, but these errors were encountered: