pg-promise usage refactoring #4400
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
initial refactoring for `pg-promise` usage.
Member
|
@vitaly-t I'm about to push index improvement for PG. |
Contributor
Author
|
@dplewis don't worry about that, there's plenty of code that's overdue for refactoring there ;) First of all, let's start moving away from promises, and into |
Contributor
Author
|
Oh wait sec, do we still not support |
Contributor
Author
|
ok, i'll better re-do the whole thing... |
Contributor
|
Yeah we’re still building targeting 6.11, i’d prefer we wait till we make 8.11 the min version to have native async await support |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
initial refactoring for
pg-promiseusage.